EhBASIC update

Talk about the operating system (EhBASIC, FAT library, ...)
lee
Posts: 12
Joined: Wed Oct 17, 2012 7:33 pm

EhBASIC update

Postby lee » Sat Dec 15, 2012 1:31 pm

Three small updates to EhBASIC fix UCASE$(), LCASE$() and USING$(). See here for details.

The version is now 3.52

Lee.

simon
Site Admin
Posts: 744
Joined: Thu Sep 13, 2012 9:35 am
Location: Luedenscheid, Germany
Contact:

Re: EhBASIC update

Postby simon » Sun Dec 16, 2012 3:24 pm

Great! Thank you Lee! :)

I should adapt the new version to Kiwi. I went with an older EhBASIC because of incompatibilities with the unix68k assembler and my impatience to address these assembler directives.

Simon

lee
Posts: 12
Joined: Wed Oct 17, 2012 7:33 pm

Re: EhBASIC update

Postby lee » Mon Dec 17, 2012 6:45 am

I should adapt the new version to Kiwi.

Yes you should, there are quite a few improvements. 8^)= The number to string routine has been modified to output up to seven significant figures, IF..THEN statements can now have an ELSE section, there is a new USING$() function for formating number output as well as some bug fixes.

I went with an older EhBASIC because of incompatibilities with the unix68k assembler and my impatience to address these assembler directives.

If you let me know what the issues are I'll see what I can do to address them while keeping the source compatible with the assembler I use.

Lee.

simon
Site Admin
Posts: 744
Joined: Thu Sep 13, 2012 9:35 am
Location: Luedenscheid, Germany
Contact:

Re: EhBASIC update

Postby simon » Tue Dec 18, 2012 10:10 pm

lee wrote:If you let me know what the issues are I'll see what I can do to address them while keeping the source compatible with the assembler I use.


When I try to assemble the actual version with unix68k I get these errors:

Code: Select all

Line 686 ERROR: Invalid opcode
Line 691 ERROR: Invalid opcode
Line 696 ERROR: Invalid opcode
Line 709 ERROR: Invalid opcode
Line 2107 ERROR: Invalid opcode
Line 2111 ERROR: Invalid opcode
Line 2495 ERROR: Invalid opcode
Line 2499 ERROR: Invalid opcode
Line 2504 ERROR: Invalid opcode
Line 2511 ERROR: Invalid opcode
Line 2548 ERROR: Invalid opcode
Line 2553 ERROR: Invalid opcode
Line 2558 ERROR: Invalid opcode
Line 2569 ERROR: Invalid opcode
Line 3104 ERROR: Invalid opcode
Line 3110 ERROR: Invalid opcode
Line 3729 ERROR: Invalid opcode
Line 3733 ERROR: Invalid opcode
Line 4807 ERROR: Invalid opcode
Line 4812 ERROR: Invalid opcode
Line 5087 ERROR: Invalid opcode
Line 5100 ERROR: Invalid opcode
Line 5106 ERROR: Invalid opcode
Line 5144 ERROR: Invalid opcode


Unix68k doesn't know about ifeq, ifne, endc. But I didn't look deeper into this issue yet.

Simon

lee
Posts: 12
Joined: Wed Oct 17, 2012 7:33 pm

Re: EhBASIC update

Postby lee » Wed Dec 19, 2012 12:01 am

Well the number of errors matches but the line numbers are off by 201, however it looks like unix68k doesn't support any sort of conditional assembly so ..

If you want nonexistant variables to return zero or a null string comment out all the code in these blocks.

Code: Select all

 ifeq  novar
. . .
 endc

Or if you want nonexistant variables to return an error comment out all the code in these blocks.

Code: Select all

 ifne  novar
. . .
 endc

If you want a null return to an INPUT command to break program execution comment out all the code in these blocks.

Code: Select all

 ifne  nobrk
. . .
 endc

Or if you want a null return to an INPUT command not to break program execution comment out all the code in these blocks.

Code: Select all

 ifeq  nobrk
. . .
 endc

You'll also need to comment out all the ifeq, ifne and endc statements.

Lee.

simon
Site Admin
Posts: 744
Joined: Thu Sep 13, 2012 9:35 am
Location: Luedenscheid, Germany
Contact:

Re: EhBASIC update

Postby simon » Thu Dec 20, 2012 12:30 pm

lee wrote:Well the number of errors matches but the line numbers are off by 201, however it looks like unix68k doesn't support any sort of conditional assembly so ..


Oh, I forgot to mention that Unix68k doesn't find the include file. Thus I just c&p its contents.

Thank you for the clarification. I would prefer the error method as it prevents one from forgetting to initialize a variable.

Simon


cron