Dear cafe,<br>Recently, I decided to use Haskell to drive the testing of a C++ DLL that we develop. After getting the FFI etc working, I thought it might be a good idea to expose an EDSL for the testers to alter the flow of invocations of the functions in the DLL. I've tried to demonstrate the approach I am contemplating here - <a href="http://hpaste.org/67495">http://hpaste.org/67495</a><br>
<br>The outcome is that I'll have a set of "Instructions" for the testers can arrange to create a sequence of calls. <br><br>> data Command = Void | Init | Get3Numbers Int Int Int| GetName String | PrintName | PrintSum | Close | PrintMessage String<br>
> deriving (Show)<br><br>> mainloop :: StateT (ScriptState Command) IO ()<br>> mainloop = do<br>> liftIO $ putStrLn "Hello World"<br>> executeCommand Init<br>> executeCommand Init<br>
> executeCommand $ PrintMessage "Enter name"<br>> executeCommand $ GetName "abcd"<br>> return ()<br><br><br>I'd like to ensure that some level of validation done. For example, if Init is called twice, the tester should get to know about it. Similarly, GeName should not be called unless PrintMessage has been called.<br>
<br>> executeCommand :: Command -> StateT (ScriptState Command) IO ()<br>> executeCommand Init = do<br>> (ScriptState c) <- get<br>> case c of<br>> Void -> liftIO $ putStrLn (show c)<br>
> _ -> liftIO $ putStrLn "Init already called"<br>> put (ScriptState Init)<br>> return ()<br>> executeCommand (GetName x) = do<br>> (ScriptState c) <- get<br>
> case c of<br>> PrintMessage _ -> do { str <- liftIO $ getLine; put (ScriptState (GetName str)); return ()}<br>> _ -> liftIO $ putStrLn "PrintMessage not called"<br>
> executeCommand (PrintMessage m) = do<br>> liftIO $ putStrLn m<br>> put (ScriptState (PrintMessage m))<br><br><br>I'd appreciate it very much if you could give me some feedback on my
approach. I get this feeling that I am wrapping up the whole program
inside a State monad - does this mean that I am giving up the functional
goodies.<br>
<br>Regards,<br>Kashyap<br>