o |
Problem: Applications running inside the J-- environment can't read user input from the console if J-- was started by double-clicking 'jmminus.jar' on Win32 platform. |
|
Workaround: Use 'run.bat', if you want to execute console applications. |
o |
Problem: Syntax coloring for Oberon doesn't support nested comments. |
|
Workaround: Don't use nested comments. |
o |
Problem: The dialog 'Options/Run Settings ...' is to long to see the 'OK' and 'Cancel' button if you're using a screen resolution of 640 x 480 pixels. |
|
Workaround: Use 'tab' and 'space' key to navigate to and press the buttons or use a higher screen resolution. |
o |
Problem: If you query data from the user within a source code template by using 'pragma getstring', 'pragma getbool' or 'pragma getfile' that is not used in the template, the data will maybe never be queried from the user. The reason for this is, that the query will be delayed until the first use of an identifier, where no value had been assigned by now. This mechanism enables the collection of queries in one dialog box. |
|
Workaround: None, since it doesn't make sense to query data that is never used. |
o |
Problem: If the path to a source directory contains a dot (like '/jdk1.2/mysource/myfile.java'), J-- is unable to track back to the error position in case of a compile error. |
|
Workaround: Use path names without dot (like '/java/mysource/myfile.java'). |