Suspect Statements

Code Rocket uses keywords in your pseudocode to determine the type of statement that is being entered. So, when the keyword changes to an unrecognised one then logically the statement becomes an assignment statement. However, this only applies to statements without any children. If you modify the keyword of a statement with no children, your statement will be flagged as suspect and turned red. When statements are in this mode, they will change type as soon as all of their children have been deleted. By doing this we can make type changes less dramatic and give you a chance to change your mind.

Consider the following pseudocode:

Syntactically valid pseudocode.

After removing the "if" keyword associated with the statement, the whole statement turns red as shown below:

Suspect pseudocode.

The statement is still regarded as an “if” statement but is in a volatile state when it no longer has any children:

Suspect statement with no children.

Anny further edits to the pseudocode will immediately transform the statement into an assignment statement.

Code Rocket Designer

From

£99.95

Standalone application for detailed software design and visualization.

More Information

Code Rocket for Visual Studio

From

£99.95

Code Rocket design support integrated with Visual Studio.

More Information

Code Rocket for Eclipse

From

£99.95

Code Rocket design support integrated with Eclipse.

More Information

Documator

From

£74.99

per year (after loyalty discount)

Add automated Code Rocket design support for your build process!

More Information