Post by: luke on July 04, 2020, 11:09:05 am
Latest source attached to this post. Project also at https://github.com/flukiluke/L-BASIC (https://github.com/flukiluke/L-BASIC) for the interested. There will be bugs, feel free to yell at me if you get an error with something that's on the "working" list.
What's different:
- Variables with the same name but different types are an error, not different variables
- No _ for INTEGER64
- It's called QUAD instead of _FLOAT
- $include should be written without a comment character or REM
What's working:
- Apostrophe comments and REM
- Line joining with :
- Variable assignment
- Arrays: multi-dimensional, arrays of UDTs.
- Array resizing, including _PRESERVE
- shared variables
- UDTs
- Optional arguments to user-defined functions
- SUBs and FUNCTIONs, including recursive calls and pass by reference
- Data types INTEGER %, LONG &, INTEGER64 &&, SINGLE !, DOUBLE #, QUAD ## and STRING $
- Addition, subtraction, multiplication, division, integer division, exponentiation, negation, MOD, AND, OR, NOT, XOR, IMP, EQV, =, <>, <, >, <=, >=
- PRINT and ?, handles ; and , as variable separators
- DO, WHILE and FOR loops
- IF THEN ELSEIF ELSE END IF (single and multi-line versions)
- SELECT CASE
- ABS, ASC (function), _ATAN2, ATN, _AUTODISPLAY
- BEEP, _BLUE32
- C* rounding functions, CALL, CHDIR, CHR$, CIRCLE, CLOSE, CLS, COLOR, COMMAND$, _COMMANDCOUNT, CONST, COS, CSRLIN, CV* functions
- DATE$ (function), DEFINT and friends, _DEFINE, _DEFLATE, _DELAY, _DEST (statement), _DEST (function), DIM, _DISPLAY (statement), DRAW
- END, ENVIRON$ (function), EOF, ERASE (one variant), EXIT, EXP
- FILES, FIX, _FONTHEIGHT, _FONTWIDTH, FREEFILE
- GET (file I/O), GOTO (line numbers only, no line labels), _GREEN32
- _HEIGHT, HEX
- _INFLATE, INKEY$, INPUT (command), INPUT$ (function), INSTR, INT
- _KEYCLEAR, _KEYDOWN, _KEYHIT, KILL
- LBOUND, LCASE, LEFT$, LEN, _LIMIT, LINE, LINE INPUT, _LOADIMAGE, LOCATE, LOF, LOG, LTRIM$
- MID$ (function), _MOUSEBUTTON, _MOUSEINPUT, _MOUSEMOVEMENTX, _MOUSEMOVEMENTY, _MOUSEX, _MOUSEY
- OPEN, OPTION _EXPLICIT
- PAINT, _PI, PLAY, POINT, PRINT, _PRINTSTRING, _PRINTWIDTH, PSET, PUT (file I/O), _PUTIMAGE
- RANDOMIZE, RIGHT$, RMDIR, RND, _RED32, _RGB, _RGB32, RTRIM$
- SCREEN (statement), SGN, SIN, SLEEP, SOUND, _SOURCE (statement), _SOURCE (function), SPACE, SQR, STATIC (statement), STR, _STRCMP, _STRICMP, SWAP, SYSTEM
- TAN, TIME$ (function), TIMER, _TITLE (statement), _TITLE$ (function), _TRIM$
- UBOUND, UCASE
- VAL
- _WHEEL, _WIDTH
What's not working:
- Arrays in UDTs
- NEXT with multiple variables on the same line 'NEXT i, j'
- Line labels
- GOSUB
- Error handling
- Events
- Line continuation with _
- Everything else
Attachments Displayed Below Message Body lbasic-v0.1.2.bas
Post by: bplus on July 04, 2020, 11:46:15 am
Post by: luke on July 04, 2020, 12:04:48 pm
Post by: bplus on July 04, 2020, 12:11:04 pm
I don't remember if Fellippe's was doing that too?
Post by: FellippeHeitor on July 04, 2020, 12:13:43 pm
Post by: Dav on July 04, 2020, 01:00:19 pm
- Dav
Post by: Pete on July 04, 2020, 01:14:52 pm
Good "luke" with the project,
Pete
Post by: bplus on July 04, 2020, 01:16:00 pm
I hope Luke has a little time to discuss beginnings, maybe another episode of QB64 talk show.
Yeah where does 65 come from? 1 more that 64?
Post by: luke on July 04, 2020, 01:21:09 pm
A lot of the constants and the DATA tables are auto-generated. See the github link for the actual sources and earlier versions.
Post by: bplus on July 04, 2020, 01:24:10 pm
I will check out the earlier versions thanks for info.
Post by: +KZ on July 04, 2020, 03:26:16 pm
Post by: SMcNeill on July 04, 2020, 03:28:03 pm
how when you find a BASIC Compiler and that need to be compiled with a BASIC Compiler and that need to be compiled with a BASIC Compiler and that need to be compiled with a BASIC Compiler and that need to be compiled with a BASIC Compiler and that need to be compiled with a BASIC Compiler......
They tend to start that way, until they mature to the point where they can self-compile. When QB64 was first being created, it was compiled with QB45, until it matured enough to start compiling itself. :)
Post by: luke on July 05, 2020, 01:26:41 am
Code: [Select]
const MAGIC_NUMBER = 17
print "Guess the number"
print "I'm thinking of a number, can you guess what it is?"
do
input "Your guess: ", guess%
if guess% > MAGIC_NUMBER then print "Nope,"; guess%; "is too high."
if guess% < MAGIC_NUMBER then print "Nope,"; guess%; "is too low."
loop while guess% <> MAGIC_NUMBER
print "Yes, you got it!"
Post by: Aurel on July 05, 2020, 03:52:25 am
That is great ...i like it !
Post by: luke on July 05, 2020, 07:21:40 am
Program from Terry Ritchie's tutorials we can now run:
Code: [Select]
DIM Value% 'numeric value the user supplies
INPUT "Enter a number between 1 and 100 >", Value%
IF Value% < 1 THEN
PRINT "That number is less than one!"
ELSEIF Value% > 100 THEN
PRINT "That number is greater than one hundred!"
ELSE
PRINT "Thank you for helping us help you help us all."
END IF
Post by: Pete on July 05, 2020, 10:11:59 am
Pete
Post by: SMcNeill on July 05, 2020, 10:28:34 am
Name it: QB60_More. Hey your fault, you asked for a pun.
Pete
Asked for a pun, not a punishment...
Post by: bplus on July 05, 2020, 12:58:46 pm
WOW man ...!
That is great ...i like it !
Ha! I was wondering if shadow man would show up for this!
Post by: Pete on July 05, 2020, 01:40:05 pm
Asked for a pun, not a punishment...
Oh come on, Steve. Everyone knows you can't spell punishment without pun... unless, of course, you spell it wrong.
Why I put up with wiseacres from Green Acres, I'll never know. ;D
Pete
Post by: Pete on July 05, 2020, 01:41:16 pm
Q-Beat64. It has a nice beat, and you can debug to it.
Pete
Post by: +KZ on July 05, 2020, 02:10:42 pm
Post by: Ashish on July 06, 2020, 03:15:57 am
I'm liking it!
The 65 source code looks complicated. ;D
Post by: luke on July 10, 2020, 08:29:26 am
Huge thanks to Ashish for finding bugs upon bugs and pointing out my sloppy coding!
Post by: johnno56 on July 10, 2020, 09:55:44 am
Post by: johnno56 on July 10, 2020, 10:15:17 am
But, that's just my opinion, for what it's worth... lol
Anyway, besides what I think, I hope that you can implement both line numbers 'and' labels without too many headaches...
I need more coffee... I think I'm babbling again...
Post by: bplus on July 10, 2020, 11:05:09 am
In reference to GOTO, please forgive my forwardness, but why? I thought 'that' bane of spaghetti-basic had been 'put down' years ago... Just the thought of a loop performing its function and told part way through to leave the loop and probably never come back... is almost 'cringeworthy' (probably not a real word - but you get what I mean). Let's not talk about how we noobs (ok me) find it difficult to translate goto's into 'basics' that no longer use line numbers... I was just getting used to using subroutines and functions and easy to follow structured listings...
But, that's just my opinion, for what it's worth... lol
Anyway, besides what I think, I hope that you can implement both line numbers 'and' labels without too many headaches...
I need more coffee... I think I'm babbling again...
Ideology goes too far when it bans practicality.
The decision that branches execution flow fundamentally requires a GOTO way down in the machine level. It would be too ironic to ban such a basic thing from Basic. But just because it's not banned doesn't give license to use it in place of ELSE, LOOP or even EXIT (ha! to Cobalt ;-)) structure because that is not practical either.
Post by: SMcNeill on July 10, 2020, 11:13:08 am
Where do you see me use them a ton??
In SUB/FUNCTIONs, as a means to clean up/restore settings before exiting.
For example, I might have a routine which tosses colored text on the screen..
FUNCTION ColoredTextAtPos (foreground, background, font, text$, xpos, ypos)
Now, the first things I want to get is:
D =_DEST: S =_SOURCE
F =_FONT
Oldx = POS(0): OldY = LOC
DC =_DEFAULTCOLOR: BG = _BACKGROUNDCOLOR
All the current settings to affect my screen...
Then I do my main process, which might have multiple exit points... If text$ = "", settings for SCREEN 0, 256 color graphic modes, and 32-bit color graphic modes, if the font is monospaced, unicode, or not....
Now some folks might sit down and scheme out some method to include/exclude all those various settings, but I tend to find it easiest to just handle them linearly one by one, myself.
IF text$ = "" THEN GOTO exit_point
IF xpos < 0 OR ypos < 0 THEN GOTO exit_point
I can't always just EXIT FUNCTION, as I may need to reset those initial values I captured, so a label called exit_point makes perfect sense a few lines before the END FUNCTION, so I can do those value resets afterwards.
It's not confusing. It's not spaghetti code. Nobody scratches their head reading it, and has a hard time understanding it. In fact, I'd argue that with proper use of a descriptive label, like exit_point above, that it's *more* readable and self-documenting than many other ways you might write the same code.
GOTO isn't inherently bad. It's just bad when it's used improperly, and then it's *really* bad.
Post by: Aurel on July 10, 2020, 11:23:20 am
...i agree
Post by: johnno56 on July 10, 2020, 07:23:10 pm
Luke. You stated, "(only line numbers for now - no labels)"... But, aren't line numbers, labels? If not what is the difference? Just curious
Post by: luke on July 10, 2020, 08:36:12 pm
There's no avoiding that it's a used statement and so needs to be implemented.
Luke. You stated, "(only line numbers for now - no labels)"... But, aren't line numbers, labels? If not what is the difference? Just curiousThe difference is in recognition. Consider this code:
Code: [Select]
10 PRINT X$
lbl: PRINT Y$It's really easy to recognise 10 as a line number - we just say if we're at the start of the line and see an integer, it's a line number.With the label, it's just a string of characters. If, instead of "lbl" I had used "BEEP", it would have not been a label but two statements joined by a colon. So far I haven't implemented the extra logic to recognise a label from a command.
Post by: johnno56 on July 10, 2020, 11:10:58 pm
Post by: luke on July 11, 2020, 11:10:30 pm
Post by: FellippeHeitor on July 12, 2020, 11:40:29 am
Post by: luke on January 15, 2021, 08:56:45 am
This means it can now run things like:
Code: [Select]
type t
a as long
b$
end type
v = 4
dim a(3, v / 2) as t
a(2, 1).a = 4
a(2, 1).b = "hello"
a(3, 2) = a(2, 1)
print a(3, 2).a; a(3, 2).bYep, that's a dynamically-sized multi-dimensional array of a user-defined type containing variable length strings.Arrays are a little untested for now, and you can't resize them. You also can't have arrays in a user-defined type, but that should be coming shortly.
Big thanks again to Ashish for implementing some commands and giving it a good test all round.
Post by: Dav on January 15, 2021, 11:11:55 am
- Dav
Post by: STxAxTIC on January 21, 2021, 04:20:32 pm
Post by: luke on January 21, 2021, 06:08:26 pm
Post by: STxAxTIC on January 21, 2021, 06:16:46 pm
Post by: Ed Davis on January 21, 2021, 09:00:00 pm
For me, all I had to change was this:
From:
# This should point to your QB64 installation
QB64 := /home/luke/comp/git_qb64/qb64 -q -w
To:
# This should point to your QB64 installation
QB64 := $(USERPROFILE)/bin/bas/qb64/qb64 -q -w
And then make does the needful.
Post by: Ed Davis on January 21, 2021, 09:45:19 pm
To get it working on Windows, I only had to make a few simple changes:
Code: QB64: [Select]
- 'If on Windows, get the temporary path
- 'Inserted after line 26
- 'Windows doesn't like ":" in filenames
- 'Changed line 68
- 'To
- 'Get rid of those pesky chr$(13) that Windows uses
- 'Inserted after line 86
- >
- >
- 'Two simple routines - probably a better way, but these work for now
- 'Inserted after line 125
- >
- >
- > do
- > loop
- > replace_char$ = s$
- >
- > dim s2$
- >
- > s2$ = ""
- > next
- > remove_char$ = s2$
Now test.bas works for me on Windows!
Post by: Ed Davis on January 21, 2021, 10:52:32 pm
I've got a rather large collection of interpreters written in basic languages ...
- Dav
Is this something you are willing to make available?
Post by: Dav on January 21, 2021, 10:59:27 pm
Is this something you are willing to make available?
I suppose I could, Ed. I think I have one by you (I recognize the name). Didn't you make the Toy Interpreter? Or something named like that...
- Dav
Post by: luke on January 22, 2021, 12:00:09 am
I really like the test.bas supplied with 65. I've been using it for some of my own unit testing, and it works great!
To get it working on Windows, I only had to make a few simple changes:
Thanks for letting me know, I'll look at adding those changes to make it cross-platform.
Post by: Ed Davis on January 22, 2021, 12:05:38 am
I suppose I could, Ed. I think I have one by you (I recognize the name). Didn't you make the Toy Interpreter? Or something named like that...Yep, I'm guilty of that one.
- Dav
I also made the infamous tiny interpreter that used to be in the QB64 sample programs directory. Someone modified it somewhat, but it still has some of my original bugs :)
You can see my original Tiny Basic post here (Feb 19, 2007, 7:16:12 AM) as part of the thread "Recommend a book on how to write a BASIC interpreter?"
https://groups.google.com/g/comp.lang.basic.misc/c/3yflBQV35M8/m/ZrPgEe8564gJ
and here:
https://narkive.com/YC5L5jHK.25
Anyway, not trying to cause you any extra work. If it is a pain to do, don't worry about it, I'll survive :)
Post by: Dav on January 22, 2021, 10:02:30 am
I got them all littered on several HD's and thumb drives. Been meaning put them all in one place one day. Maybe now is a good time....
- Dav
Post by: Aurel on January 24, 2021, 12:39:39 pm
Your coditor ...oups code editor is great and i was using it before I
modify my own to work with qb64...
so i hope that you will show us your collection
Post by: luke on January 09, 2022, 07:02:57 am
This version can create SUBs and FUNCTIONs, with the catch that if you put the SUB/FUNCTION at the bottom of your program, you'll need a DECLARE SUB or DECLARE FUNCTION line at the top. Or, just put the SUB itself at the top of your program (that's perfectly legal in L-BASIC).
You can also have optional arguments! Example:
Code: [Select]
sub s(a, option b, option c)
print "a = "; a;
if option(b) then print "b = "; b;
if option(c) then print "c = "; c;
print
end sub
s 1
s 2, 3
s 2, 3, 4
s 2, , 4
Other working features include array resizing including _preserve, and DIM SHARED support.
Attachments Displayed Below Message Body lbasic-0.1.0.bas
Post by: madscijr on January 14, 2022, 01:42:55 pm
The big trick for making my old TI programs work in QB64 would be replicating the sound commands. Which leads to my wishlist item for native ADSR waveform sound commands for QB64!
Post by: luke on January 16, 2022, 06:48:50 am
I'm happy to report DECLARE SUB/FUNCTION lines are no longer needed. You can arrange your code however you want, so this is fine:
Code: [Select]
Sub s1
s2
End Sub
s1
Sub s2
Print "Hi"
End SubSELECT CASE is now implemented, including CASE IS and CASE x TO y forms.
$includes are handled, but unlike QB64 they should not go in a comment. The $ is the first character on the line, like with $checking or $screenhide in QB64.
This version is actually capable of running STxAxTIC's Sanctum 3D simulator with some very minor tweaks. Unfortunately it's rather slow - but a success nonetheless.
Full list of commands in the first post.
Attachments Displayed Below Message Body lbasic-v0.1.1.bas
Post by: bplus on January 30, 2022, 10:53:21 am
Code: QB64: [Select]
- ' test recursive sub on Luke Basic b+ 2022-01-30
- recurs 1, 0, 0, 1
- x! = a!
- y! = b! + a!
- z! = y! + c!
- Print "Level:"; level%
- recurs x!, y!, z!, level% + 1
Post by: jack on January 30, 2022, 12:53:42 pm
you can make it work by changing line 11 to call recurs (x!, y!, z!, level% + 1)
but granted it's different than QB64
Post by: bplus on January 30, 2022, 12:57:44 pm
Post by: Phlashlite on February 01, 2022, 11:00:41 pm
Post by: luke on February 05, 2022, 08:42:42 am
Attachments Displayed Below Message Body lbasic-v0.1.2.bas