Project: StateCharts cOmPilEr (SCOPE)
Release: scope-0-16_final
     
     Copyright (C) 2001-2004 Andrzej Wasowski
     
     This program is free software; you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
     the Free Software Foundation; either version 2 of the License, or
     (at your option) any later version.
     
     This program is distributed in the hope that it will be useful,
     but WITHOUT ANY WARRANTY; without even the implied warranty of
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
     GNU General Public License for more details.
     
     You should have received a copy of the GNU General Public License
     along with this program; if not, write to the Free Software
     Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

release-0.16.txt,v 1.1 2004/05/13 20:41:27 wasowski Exp

See MANUAL for installation, usage instructions and credits.
See LICENSE for usage license.

RELEASE NOTES

This is a bug fix release. It does not contain any feature extensions
from 0.15. It should be easier to build though.

MAIN BUG FIXES AND NEW FEATURES

* several fixes in the build system, so that all test cases and
  regression tests are passed now.

* several fixes in the build system, so that interactive debug mode
  works again.

	
LIST OF KNOWN PROBLEMS

* Only 4.x input file format is supported (ver 5.x is under way)

* A quiet assumption that state names are different than event names.

* I use some extentions of Moscow ML (module language) which makes the
  thing harder to port (but isn't that in the code that is not used anyway?)

* Only models containing a single system are supported (no multi-system
  models at the moment).
        
* Internal rules are ignored (not even a warning is issued) 

* Similarly Do reactions are ignored (Termination transition causes a
  parse error).
        
* Types with absolute values longer than 31 bits are not handled
  (VS_UINT32, VS_INT64, VS_UINT64).

* Variable ranges are not checked at runtime (even in debug version
  code).

* Transition conflicts are not resolved (the model is assumed to be
  conflict-less which you can verify with original visualSTATE
  verifier).

* Signals (aka internal events) may not have parameters (but they cannot
  either in the actual IAR visualSTATE).

* No debug (test) drivers for VS compatibility mode

* VS compatibility mode drivers do not integrate smoothly (you still
  need to do a lot of handwork to compile VS model, though less than
  before).

* No parse error messages (at least for the moment).  
	
* In hierarchical code generation (-cC1) Model reinitialization does
  not properly work for history states, i.e. history states are
  reinitialized to recent value of history instead of to the initially
  indicated state. Actually I am not sure what UML semantics expects,
  but probably it does not consider reinitialization, which means it
  expects full reinitialization. Only models with history which need
  to be reinitialized at runtime (not restarted, which is a different
  thing) suffer from this bug.