Two errors associated with too long command name
Here is a module that generates two errors. Description of errors is written inside module.
MODULE longcommandname; (*! This bug was found in revision 9696. First procedure in this module generates error 'Command name too long' (well, the name is really too long but how long is it allowed to be? Where is the length being specified?) With this first procedure generating error the second procedure becomes invisible. It generates error: not found! Removing first procedure with long name makes the second procedure visible again. *) (*! this procedure generates error: WMTextView: Command parsing error, res: 3903 (Command name too long) *) PROCEDURE toolong123456789012345678901234567890*(); BEGIN HALT(100); END toolong123456789012345678901234567890; (*! If the procedure above generates error 'Command name too long' it also masks visibility of following procedure. Procedure test() generates error: WMTextView: Command execution error, res: 3901 (Command longcommandname.test not found) *) PROCEDURE test*(); BEGIN HALT(101); END test; END longcommandname. longcommandname.toolong123456789012345678901234567890 ~ longcommandname.test ~ System.Free longcommandname ~