GreenScript

System-level hardware modeling becomes more important each day. A lot of effort is done nowadays to leverage the abstraction level and simplify the architecture exploration. The GreenScript project aims in this direction, by making legacy SystemC models to interoperate with higher abstraction level models done in scripting languages.
The motivation is to be able to explore the advantages of a dynamically-typed language with garbage-collection in the context of systems modeling, recognizing that model development time is often more important than model run time, especially for system architecture exploration. GreenScript simulations are expected to run much slower than SystemC simulations and this is considered acceptable. The idea is that GreenScript can be used when a model is needed very quickly or for coding parts of a model that are activated very infrequently and thus have no significant impact on the overall simulation speed.
The syntax provided to the user will remain as close as possible to SystemC, and semantics of events, threads, scheduling, delta cycles and so on should be the same in GreenScript and SystemC. The user interface is composed by classes and functions under the module gs.
At the time of this writing, only the Python interface is available. This project is in beta stage. There may be changes in the interfaces described in this document to accommodate particularities of other scripting languages like Perl, TCL, etc.
For examples how to use this interface, please take a look at the examples directory. To run, import the example inside python or use python example.py. The embedded examples have to be compiled and run outside Python.


Documentation:


Release List:
package lableStabilityDateProjectArchitectureQuality
greenscript/0.2.1/bareUnstable (Not tested yet)7 May 08GreenScriptall
greenscript/0.2.1Unstable (Not tested yet)7 May 08GreenScriptall
greenscript/0.2/bareUnstable (Not tested yet)11 Apr 08GreenScriptall
greenscript/0.1/bareUnstable (Not tested yet)7 Feb 08GreenScripti386
Mail List: 
This group has an email list, all issues will be sent to all members of the group