04-28-2022, 05:03 PM
(04-27-2022, 04:38 PM)Pete Wrote:(04-27-2022, 04:27 PM)Tim Wrote:(04-27-2022, 06:35 AM)admin Wrote: BAS, in this case is QB64 *.bas files. You can find our source files inside the internal/source folder, and internal/c folders, included with all versions of QB64.
Could QB64 be completely coded/recoded using QB64 only?
I don't develop QB64, but I don't see how it could be just QB64 statements. It translates code from QB64 to C/C++, and then uses an open source compiler to compile that code, and runs the program. So without any C/C++, how could it translate, right? I believe to covert to binary would mean translating to ASM or worse, machine code. Anyway, just spit-balling here. I've never really delved into it, but it will be interesting to see if this sparks some conversation from those who have.
Pete
fyi, from Wikipedia:
Quote:QB64 was originally compiled with QuickBASIC 4.5. After significant development, Rob Galleon, the developer, became hindered by QuickBASIC's memory limitations and switched to Microsoft Basic PDS 7.1, which solved these problems for a short time.[5] After version 0.63, QB64 was able to compile itself so the conventional memory limitations no longer applied.
So it sniffs like QB64 is used, i.e. BASIC code, to create QB64.
QB64 compiles itself. How it gets from point A-Z makes for interesting factoid, but that's pretty much it. One doesn't need another language and compiler, in addition to QB64, to compile QB64. A QB64 install, QB64 itself, doesn't need any extras.
Well, that's what I'm reading into it.