Difference between revisions of "AMOS:Bugs"
Spellcoder (talk | contribs) (Added the bugs I know of in AMOSPro & AMOSPro Compiler) |
Spellcoder (talk | contribs) (many if's -> many *else*if's causes problems with the compiler) |
||
Line 1: | Line 1: | ||
==Compiler bugs== | ==Compiler bugs== | ||
− | * many | + | * many elseif's causes problems with the AMOS(Pro) compiler? |
* many data statements causes problems with the AMOS(Pro) compiler? | * many data statements causes problems with the AMOS(Pro) compiler? | ||
Revision as of 08:57, 25 September 2007
Compiler bugs
- many elseif's causes problems with the AMOS(Pro) compiler?
- many data statements causes problems with the AMOS(Pro) compiler?
Using the Input command with a too long text
(Discovered by Spellcoder, somewhere before 2000)
If you use a text that's so long it'll reach the end of the screen, AMOS(Pro) will hang for a while. How long the text needs to be for this to happen seems to depend on the width of the screen.
Screen Open 0,320,200,4,Lowres Input "ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!?";A$
This example uses 38 chars (so it's 38*8 pixels = 304 pixels width).
The cursor is also 8 pixels (304+8=312).
(not tested yet if it happens earlyer if you place the cursor in the middle of the screen)
Can't write %111111111111111111111111111111111
(Discovered by Spellcoder, 24 sep 2007)
If you write %111111111111111111111111111111111, AMOS will change it in 10