BEX v1.00 bugs!

[oompa loompa]

Here's a list of bugs that I've already encountered in v1.00. Please add to this list or post some bugs if you've found anything (even any little thing)! I have most of these bugs already fixed, hehe, just waiting for more bugs. Post some small features that you guys want, that would make bex coding easier

Recursizing user-defined functions is broken, eg:
a = add(7, add(1,3))
print a

declare function add(a, b)
return a+b
end function


- Fixed the <tt>READ</tt>, and <tt>READINT</tt> commands when using long variables.<br>
- Added support for arrays in the commands <tt>READ</tt>, <tt>READINT</tt>, <tt>READLONG</tt>, <tt>GETS</tt><br>
- Fixed the <tt>GETS</tt> command to not declare integer or long variables that are very big<br>
- Improved the <tt>INPUT</tt> command to be more BASIC like<br>
- Added lower case letters to the <tt>INPUT</tt> command. Press the C button to switch between lower case letters and upper case<br>
- Fixed a major bug with storing data with the <tt>DATA</tt> command.<br>
- Fixed a bug with the <tt>Mid$</tt> function, which was broke in v1.00 of the compiler<br>
- Fixed a compiler bug when opening a souce file that is in a completely different drive<br>
- When a file has successfully compiled, the ending dialog will now show the time that was spent assembling the source with the SNASM assembler<br>
- Fixed the VarPtr&() Function to work with the newer array data types<br>

- Will possible remove the regmove set of commands, since user-defined assembly functions/subs are much better
- Added support for assembly targetted functions/subs. It already exists in v1.00, but I have improved it, and have added documentation
- Fixed support for using more than 3 arguments in user-defined functions/subs

[Shiru]

About features. For me, it's very disturbing that every time after compilation BEX shows message box (with that annoying sound), and force me to click button/press enter. I think, it would be better, if BEX will just show this message in log window.

[Mairtrus]

I found an error in the declaration of multi-dimensional arrays quite some time ago: When you declare an array over 8 dimensions, when you click the button Memory Map, BEX dies. i.e.:
Dim MyArray(1,1,1,1,1,1,1,1,1) as Integer
Maybe no one needs a very large array, but ...

Another thing I found (although I don't know if it is an error) is in the use of "argunerics" :no longer returns a value of 1 or 0(like BEX v0.21). Instead, returns crazy values. For example, when used to determine which buttons of the Joypad are being pressured, it returns a value of 255, and, in other projects, I obtained values of 45786 or similar(not in the joypad) .

[oompa loompa]

About features. For me, it's very disturbing that every time after compilation BEX shows message box (with that annoying sound), and force me to click button/press enter. I think, it would be better, if BEX will just show this message in log window.

I can add a very quick option to turn the end-compilation status off

Dim MyArray(1,1,1,1,1,1,1,1,1) as Integer

bex will actually support that . The error is with the memory map viewer, because there's not enough room in the string that shows the dimmensions. I'll fix it anyways. Same thing happens, if you declare a variable with a name that is extremely huge.

Another thing I found (although I don't know if it is an error) is in the use of "argunerics" :no longer returns a value of 1 or 0(like BEX v0.21). Instead, returns crazy values. For example, when used to determine which buttons of the Joypad are being pressured, it returns a value of 255, and, in other projects, I obtained values of 45786 or similar(not in the joypad) .

I'll fix that also. It was a speed optimization, since the value of 0 will always be false, and any other value will be whatever.

Also, here are more bugs I found:

- Fixed expressions having the form: str$(val(a)+val(b)), str$(val(a)<<val(b)), and str$(val(a)>>val(b))<br>
TODO - <tt>Print 1*65536</tt> is broken<br>
- String comparisons reseted the heap (for garbage collection), which is not good, eg: print "Word "+str$("asdf"="asdf")+" Hello" will only print "Hello"

Here's what i'm working on (but not might be in the next release, which will be released within a week):

- Adapting snasm syntax to asmx assembler
- Working on an optimizer program, to optimize assembly, so bex can be just as fast as c. stuff like:

movem.l d0/d1/d4,-(a7)
clr.l d0
jsr joypad
movem.l (a7)+,d0/d1/d4

into (much much faster):

clr.l d0
jsr joypad

or

move.l #1,d0
move.w d0,(__INTEGER_c)

into:

move.w #1,(__INTEGER_c)

[oompa loompa]

Update:

I now have asmx successfully assembling basiegaxorz programs! I had to make a few changes to the asmx sources to make it work with bex's crappy assembly source though, and I don't believe that asmx will optimize some of the simpler assembly stuff (eg: clr.l d0 into moveq #0,d0). I'll have to contact the author regarding distribution

Everyone, say goodbyte to snasm - well, soon. For now, more bug testing will have to be done, so it won't be in the next release