|
Posted
over 16 years
ago
by
Charles Rapp
SMC
The State Machine Compiler
(Version: 5.0.1)
http://smc.sourceforge.net
0. What's New?
--------------
New Features:
+ (Groovy)
Added support for Groovy programming language (-groovy).
Examples not yet available.
Major changes:
+ (Java)
Added state
... [More]
change notification to FSMContext.
(SF feature request 1570050)
+ (Programmer's Manual)
Added section 12: Event Notification which explains how state
change notification can be used in Java.
Minor changes:
None.
Bug Fixes:
+ (C++)
Changed <string> include to <cstring> and fully qualified
strncpy to std::strncpy.
(SF bug 1708488)
+ (C, C++)
Corrected C and C++ FSM header file include.
(SF bug 1699854)
+ (C)
Corrected error which generated incorrect C code when state
names began with a lower case letter (state "connected"
would generate uncompilable C code while "Connected" did
not).
(SF bug 1751740)
+ (Programmer's Manul)
Corrected C# example code in section 7.
(SF bug 1711484)
+ (Python)
Corrected error where a "pass" clause was incorrectly
inserted in a non-empty method body of an actionless,
unguarded, push transition was compiled without the
-g option.
+ (Compiler)
Reading in files as Java chars rather than bytes.
Java char type is UTF-16 code unit and correctly
handles 16-bit characters.
(SF bug 1773868)
+ (GraphViz)
When using -glevel 2, a parameterless transition will
appear to have parameters if the previous transition
has parameters.
(SF bug 1823635)
1. System Requirements
----------------------
+ JRE (Standard Edition) 1.5.0 or better.
+ Whatever JRE's requirements are (see http://java.sun.com/j2se/
for more information).
2. Introduction
---------------
If you use state machines to define your objects behavior and are
tired of the time-consuming, error-prone work of implementing
those state machines as state transition matrices or widely
scattered switch statements, then SMC is what you're looking for.
SMC takes a state machine definition and generates State pattern
classes implementing that state machine. The only code you need
to add to your object is 1) create the state machine object and
2) issue transitions. ITS THAT EASY.
+ NO, you don't have to inherit any state machine class.
+ NO, you don't have to implement any state machine interface.
YES, you add to your class constructor:
_myFSM = new MyClassContext(this);
YES, you issue state transitions:
_myFSM.HandleMessage(msg);
Congratulations! You've integrated a state machine into your
object.
SMC is written in Java and is truly "Write once, run anywhere".
If you have at least the Java Standard Edition v. 1.5.0 loaded,
then you can run SMC (if you have the Java Enterpise Edition, so
much the better!)
Java Standard Edition can be downloaded for FREE from
http://java.sun.com/j2se/
SMC currently supports ten programming languages:
1. C,
2. C++,
3. C#,
4. Java,
5. Lua,
6. Objective-C,
7. Perl,
8. Python,
9. Ruby,
10. [incr Tcl] and
11. VB.Net.
SMC is also able to generate an HTML table representation of your
FSM and a GraphViz DOT file representation
(http://www.graphviz.org).
3. Download
-----------
Surf over to http://smc.sourceforge.net and check out
"File Releases". The latest SMC version is 3.0.0.
SMC downloads come in two flavors: tar/gzip (for Unix)
and self-extracting zip file (for Windows).
The download package contains the executable Smc.jar and
supporting library: statemap.h (for C++), statemap.jar
(for Java), statemap.tcl & pkgIndex.tcl (for Tcl),
statemap.dll (for VB.Net) and statemap.dll (for C#).
NOTE: Only the SMC-generated code uses these libraries. Your code
doesn't even know they exist. However, when compiling your
application, you will need to add a
-I<path to statemap.h directory>
or
-classpath ...:<path to statemap.jar>
to your compile command (when running you Java application, you
also need to add statemap.jar to your classpath).
The download package's directory layout is:
Smc -+-LICENSE.txt
|
+-README.txt
|
+-bin---Smc.jar
|
+-docs--SMC_Tutorial.pdf
|
+-lib-+-statemap.h
| |
| +-statemap.jar
| |
| +-setup.py
| |
| +-statemap.py
| |
| +-C---statemap.h
| |
| +-CSharp-+-Debug-+-statemap.dll
| | | |
| | | +-statemap.pdb
| | |
| | +-Release-+-statemap.dll
| |
| |
| +-Lua--+-README
| | |
| | +-statemap.h
| |
| +-ObjC-+-README.txt
| | |
| | +-statemap.h
| | |
| | +-statemap.m
| |
| +-Perl-+-MANIFEST
| | |
| | +-Makefile.pl
| | |
| | +-README
| | |
| | +-Statemap.pm
| | |
| | +-test.pl
| |
| +-Ruby-+-README
| | |
| | +-statemap.rb
| |
| +-VB-+-Debug-+-statemap.dll
| | | |
| | | +-statemap.pdb
| | |
| | +-Release---statemap.dll
| |
| +-statemap-+-FSMContext.class
| | |
| | +-State.class
| | |
| | +-StateUndefinedException.class
| | |
| | +-TransitionUndefinedException.class
| |
| +-statemap1.0-+-statemap.tcl
| |
| +-pkgIndex.tcl
|
+-misc-+-smc.ico (smc Windows icon)
|
+-examples-+-Ant--+-EX1 (Java source code, Ant built)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| | |
| | +-EX5
| | |
| | +-EX6
| | |
| | +-EX7
| |
| +-C----+-EX1 (C source code, Makefiles)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| |
| +-C++--+-EX1 (C++ source code, Makefiles)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| | |
| | +-EX5
| | |
| | +-EX6
| |
| +-CSharp-+-EX1 (C# source code)
| | |
| | +-EX2
| | |
| | +-EX3
| |
| +-Java-+-EX1 (Java source code, Makefiles)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| | |
| | +-EX5
| | |
| | +-EX6
| | |
| | +-EX7
| |
| +-Lua--+-EX1 (Lua source code)
| | |
| | +-EX2
| | |
| | +-EX3
| |
| +-ObjC-+-EX1 (Objective C source code)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| | |
| | +-EX5
| | |
| | +-EX7 (Mac OSX XCode Project)
| |
| +-Perl-+-EX1 (Perl source code)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| | |
| | +-EX7
| |
| |
| +-Python-+-EX1 (Python source code)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| | |
| | +-EX7
| |
| +-Ruby-+-EX1 (Ruby source code)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| | |
| | +-EX7
| |
| +-Tcl--+-EX1 (Tcl source code)
| | |
| | +-EX2
| | |
| | +-EX3
| | |
| | +-EX4
| | |
| | +-EX5
| |
| +-VB---+-EX1 (VB.Net source code)
| |
| +-EX2
| |
| +-EX3
| |
| +-EX4
|
+-tools-+-maven-+-plugin.jelly
| |
| +-plugin.properties
| |
| +-project.xml
|
+-smc-anttask-+-.classpath
|
+-.project
|
+-build.xml
|
+-smc-anttask.iml
|
+-smc-anttask.ipr
|
+-smc-anttask.iws
|
+-build---classes---...
|
+-dist---smc-ant.jar
|
+-lib---ant.jar
|
+-src---net---sf---smc---ant---SmcJarWrapper.java
4. Installation
---------------
After downloading SMC (either tar/gzip or self-extracting zip
file), you install SMC as follows:
1. Figure out where you can to load the Smc directory and place
the SMC package there.
2. If you already have an "smc" directory/folder, change its name
to something like "smc_old" or "smc_1_2_0". This will prevent
its contents from being overwritten in case you want to back
out of the new version. Once you are satisfied with the new
version, you may delete the old SMC.
3. Load the SMC package:
(Unix) $ tar xvfz Smc_4_0_0.tgz
(Windows) running Smc_4_0_0.zip
You're done! There really is nothing more that needs to be done.
You may want to take the following steps.
+ Add the full path to .../Smc/bin to your PATH environment
variable.
+ Add the full path to statemap.jar to your CLASSPATH environment
variable.
+ Add the full path to .../Smc/lib to your TCLLIBPATH environment
variable.
The tools directory includes a Maven plug-in
(http://www.maven.org) and an ant task to help integrate SMC
into other development environments.
An Eclipse plug-in is not yet available.
5. Examples
-----------
The examples directory contains example SMC-based applications.
The examples range from trivial (EX1) to sophisticated (EX5).
Use these examples together with the SMC Programmer's Guide to
learn how to use SMC.
The C++ examples provide Makefiles, Microsoft DevStudio 6.0
workspace and DevStudio 7.0 solution.
The Java examples in examples/Java use "make" for building.
The same examples also appear in examples/Ant and use "ant".
The [incr Tcl] examples are not built and require you to
execute "java -jar Smc.jar" by hand.
The VB.Net and C# examples use DevStudio 7.0.
To learn more about each example and how to build & run each one,
read the example's README.txt.
6. FAQ/Documentation/Reporting Bugs/Latest News
-----------------------------------------------
Surf over to http://smc.sourceforge.net to:
+ Read the SMC Frequently Asked Questions (FAQ).
+ Download documentation - including the SMC Programmer's Guide.
+ Talk with other SMC users in Public Forums.
+ Report bugs.
+ Get the latest news about SMC.
+ Access SMC source code via a CVS web interface.
+ Check out docs/SMC_Tutorial.pdf.
7. Notices
----------
This software is OSI Certified Open Source Software.
OSI Certified is a certification mark of the Open Source Initiative. [Less]
|
