Hm, looking into the sourcecode, this error should have been fixed already. Maybe a new build for the ATARI will be all which is needed. (Yes, it looks like it is an endianess problem). My life would be more easy, if someone with an ATARI could help. I myself do not use any anymore. So I cannot really test it. X11-Basic on ATARI is very slow, because I use the overhead from ARARI-MINT. To get rid of this, a lot of optimizations would be necessary. Is it worth it?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does xbasic still maintain source code compatibility with Atari? What about binary data file compatibility between Atari, ARM, and x86? Should I make certain to use the MK and CV functions and string buffers when working with BGET and BPUT, or does the Mark Williams Company still have a stealthed submarine patent on canonical byte ordering for cross-platform interoperability? Will my dalliance with VarPtr(Buffer%(0, 0, 0, 0)), Dim?(Buffer%()) * 4 only lead to my doom? What about SEEKing 'too far' past the end of a file before a BPUT? Is that acceptable behavior here but beyond the pale there? Fine for "U" but iffy for "A" and right out for "O"?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to test the Atari port, but ran into a problem.
Rather than re-write it, its noted here:
http://www.atari-forum.com/viewtopic.php?f=69&t=27042&p=263885#p263885
Hm, looking into the sourcecode, this error should have been fixed already. Maybe a new build for the ATARI will be all which is needed. (Yes, it looks like it is an endianess problem). My life would be more easy, if someone with an ATARI could help. I myself do not use any anymore. So I cannot really test it. X11-Basic on ATARI is very slow, because I use the overhead from ARARI-MINT. To get rid of this, a lot of optimizations would be necessary. Is it worth it?
I have made a new build (1.23-16-st). Maybe it works now.
Does xbasic still maintain source code compatibility with Atari? What about binary data file compatibility between Atari, ARM, and x86? Should I make certain to use the MK and CV functions and string buffers when working with BGET and BPUT, or does the Mark Williams Company still have a stealthed submarine patent on canonical byte ordering for cross-platform interoperability? Will my dalliance with VarPtr(Buffer%(0, 0, 0, 0)), Dim?(Buffer%()) * 4 only lead to my doom? What about SEEKing 'too far' past the end of a file before a BPUT? Is that acceptable behavior here but beyond the pale there? Fine for "U" but iffy for "A" and right out for "O"?
A new version is out. 1.27-62 See here: https://codeberg.org/kollo/X11Basic/releases