| OCR Text |
Show 131 E.3 ASSASSIN Messages The following is a brief description of the error messages which may be generated during the course of parsing or simulation: - "No TO States": no next state was specified in a transition statement in the SICUDL program. - "Identifier <id> is Reserved": indicates that the in:put or state named <id> is already used somewhere in the system and must be changed or the system will be damaged. This should go away in future versions where packages are used. - Also, such names could be altered so that no conflict occurs. - "Output <id> is Object of Type Contention": indicates that the output named <Ld> is the object of Ooth HOLD and SET or RESET operations. The compiler will not be able to resolve all of these and wi],.l not generate any code until all such contentions are resolved.· - -- - "Joins Not Matched": indicates that all states in a join transition do not all .indicate that they join. That is, the union of their joining states lists is not equal to the union of their state names. - "State <id> has more than one valid transition": indicates that in the current control-u.it state, the state with name <id> has two transitions which will occur. This Violates tbe semantics of one-hot state-machines. - "Input Name <id> is too long": indicates that the simulator cannot fit the input name <Ld> in the width of the window which displays the input names and values. The simulator will still operate, but the value of that input will not be visible on the screen. - "State Name <id> is too long": indicates that the simulator cannot fit the state name <Ld> in the width of the window which displays the state names and values. The simulator will still operate, but the value of that state Will not be visible on the screen. _ "Output Name <io> is too long": indicates that the simulator cannot fit the output name <id> in the width of the window which displays the output names and values. The simulator will still operate, but the value of that output will not be visible on the screen. "Corrections to Input File Required No Simulationn: indicates that the building of the data structures was not |
