Denial

Hi all, Just for the fun of it: programming recursive functions in CBM Basic cannot be done - it leads to an ?OUT OF MEMORY error. BUT In WimBasic it can be done. For example, calculating a factorial: 10 A$(0)="1" 20 A$(1)="I*FNF(I-1)" 30 DEF FNF(I)=EVAL A$(SGN(I)) 40 PRINT FNF(3...

Hey chysn,

It is great to see the fruits of my efforts being used across the world!
Please let me know what you find!

Regards,

Wim.

Mike's comment is completely correct, so I would go for that. To answer your question: In WimBasic an EXEC "GOTO"+STR$(A) works as intended should you choose to use a computed GOTO. EXEC "GOSUB"+STR$(A) may run into problems in some scenarios because of the GOSUB stack frame inte...

Hello all, A new version of WimBasic has been released. It is available at http://wimbasic.webs.com A new command has been added: ERASE. This deletes an array that was previously DIM'd. Useful when memory is scarce, an array needs to be reinitialized with zeros or empty strings, or needs to be redim...

Below is the ML-code behind he INSTR-function in WimBasic. The function searches a substring in a larger string, with an optional starting position. The result is 0 when not found, non-zero is the location of the substring in the larger string. Regards, wimoos ; ; Perform INSTR ; LA776 JSR $CEFA ; c...

I did some minor concessions on the previous version of WimBasic to make space for this new command. The current version now supports the ERASE command. The concessions are that the TOGGLE command is removed and that MERGE no longer prints the text 'MERGING'. ERASE removes a previously dimensioned a...

PM sent

Hi all, Unfortunately, I couldn't make this part of WimBasic. But the code is fully relocatable, so this opens up possibilities. The tapebuffer is large enough to hold the code. I ran some tests now and it works as expected. Removing an array can be useful when memory is scarce, or when an array nee...

Fixed it, thanks for your remark. The prg was also included in the zipped autoboot disk in my previous post.
@moderator: Sorry for hijacking this subject.

Regards,

Wim.

Not much math needed:

I optimised ViCalc in WimBasic. It is now less than 70 lines and a little over 2k in size. I added an autoboot D64 in the zip file. It still works conform the manual I found some bugs that I fixed, and I used WimBasic features like ROUND, EVAL, INSTR, PRINT@ and SWAP. This makes it more responsive. ...

I have looked into ViCalc. Its slowness is more due to the way the screen is handled (cursor movement), than to the length of the program (it is a little bit less than 100 lines). Performance improvements could be done by changing 'IF <cond1> AND <cond2>' into 'IF <cond1> THEN IF <cond2>' constructs...

Update: I understand why the mismatches might not matter, though. My test program goes strictly "by the book" (The VIC-20 user manual). If you can't type a character on the keyboard, does it even matter? Maybe, maybe not. For my application, I'd rather convert everything, because I can th...

This does the trick:

WimBasic is still at your disposal. Next to SET, RESET and POINT it already supported, I have also added TOGGLE.

For the use of the '9-th color' there is the command AUXCOL to set this color in 36878. The CURSOR command sets the color in 646.

Regards,

Wim.