{*} Other simulation signatures


The simulation function that exists currently is described as:

  val simulate : symbolic_module_t -> string -> int -> string -> unit

  Parameter 1 is a Ticc module
  Parameter 2 is an expression representing the starting state
  Parameter 3 is the number of cycles to simulate
  Parameter 4 is the name of the file that should contain the simulation results

Does the second parameter allow using names of statesets that are defined in the .si file?

Sending the output to a file (fourth parameter) is good, but it might be more useful (for a debugger, for instance) if the fourth parameter is a function that gets called with each line of output. This function might be even more useful (for a debugger) if it returned the "preferred" action that the user would like to have taken next.

TiccFeatureReq/Other simulation signatures (last edited 2006-01-27 18:29:36 by BoAdler)