Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
I dare you...
#21
The SICK64 example is trying to jump out of both "FOR... NEXT" loops. "EXIT FOR" would just jump out of the innermost one, and after that it would require an IF statement to check a flag in the least so it could jump out of the outer loop. While inside the innermost loop must have a flag which is usually set to zero, and set to -1 or 1 only for the purpose of breaking out of "everything". That's so that the flag could be checked later.

Otherwise use "GOTO". (shrugs)

Freebasic could do "EXIT FOR, DO, FOR, DO" which is more typing and confusing, but some people like many levels of nesting in their parsers and other such routines.
Reply
#22
well ..i don't have (yet) in my interpreter for/next loop ..so i use while/wend
btw
i use GOTO when ever i can or when there is no other options

also i never investigate SICK64 code to much..what i know is that is little bit bloated
well some functions have purpose ..just to be clear ..but from my side my own missing
some things and is not written in FreeBasic than in o2..
making reference to FB ..it is different type of lang than qb64 in many things .
Reply
#23
well Erik interpreter is really large 24 000 lines of code ..WOW
Ed subsetQB written in is 3100 LOC
my written in o2 is 2400 LOC
Reply
#24
Quote:eoredson you'll have to edit your documentation a bit, the code example has "NEXT" where there should be a "NEXTIF" to match the "FORIF", I think because I haven't tried it, I have to go back to Windows to test 32-bit stuff, don't like doing it with Linux/Wine.


Sorry, there are some mismatched Forif/Nextif in the sample code.
Reply
#25
Quote:well Erik interpreter is really large 24 000 lines of code ..WOW


@aurel: If you think that is alot of code you should check out my QB shell at:

https://qb64phoenix.com/forum/showthread...3#pid10893
Reply
#26
hey @aurel what happened to your forum?  where can I find microA updates now?
Reply
#27
@ hey vince
i think that you know "what happened" ..but that is not for this topic
latest update is on sourceForge.

@erik
well the fact is that is large Wink

Uff ..if i remove error preScan i think i can squash it into 1500 or less in qb64

i will see
Reply
#28
(03-17-2023, 07:22 AM)aurel Wrote: @ hey vince
i think that you know "what happened" ..but that is not for this topic

I must've missed it, what did bplus do this time?
Reply
#29
Quote:Uff ..if i remove error preScan i think i can squash it into 1500 or less in qb64


With qb64shell.bas at 43,889
and qb64shell.inc at 1,317 lines

I don't think so. Huh
Reply




Users browsing this thread: 3 Guest(s)