Stateflow User's Guide

Parser Error Messages

The Stateflow parser flags syntax errors in a state chart. For example, using a backward slash (\) instead of a forward slash (/) to separate the transition action from the condition action generates a general parse error message.

Typical parse error messages include the following:

• "Invalid state name xxx" or "Invalid event name yyy" or "Invalid data name zzz"

• A state, data, or event name contains a nonalphanumeric character other than underscore.

• "State name xxx is not unique in objects #yyy and #zzz"

• Two or more states at the same hierarchy level have the same name.

• "Invalid transition out of AND state xxx (#yy)"

• A transition originates from an AND (parallel) state.

• "Invalid intersection between states xxx and yyy"

• Neighboring state borders intersect. If the intersection is not apparent, consider the state to be a cornered rectangle instead of a rounded rectangle.

• "Junction #x is sourcing more than one unconditional transition"

• More than one unconditional transition originates from a connective junction.

• "Multiple history junctions in the same state #xxx"

• A state contains more than one history junction.

Error Messages

Code Generation Error Messages

© 1994-2005 The MathWorks, Inc.