Welcome Guest. Please Login or Register. Apr 6th, 2018, 12:12am
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
If you require a dump of the post on your message board, please come to the support board and request it.
It does (of course) produce standalone EXEs, but not DLLs.
Now you got me very confused, as previously you wrote:
Quote:
In any case BBC BASIC is interpreted, so there's no conventional 'compiling' or 'linking' involved:
Or by this:
Quote:
the 'program' is treated as data
Do you mean that the basic source file is included (possibly as tokens) then your "compiler" takes parts or the whole of BBCWRUN.EXE and creates another exe with these tokens as included data?
Sorry to be a pain with all these questions but I'm trying to understand the process.
Sorry to be a pain with all these questions but I'm trying to understand the process.
A BB4W executable consists of the run-time engine (code) plus the tokenised/compressed BASIC program (data) bound into a single Portable Executable file. Also incorporated in the EXE are embedded library and resource files (if any), an icon and a manifest. It is also possible to incorporate other resources, such as version information, by means of REM!Resource compiler directives.
None of this is particularly out-of-the-ordinary. Installer/setup programs typically create similarly-structured EXEs, because they too combine multiple compressed files plus an extract/install program in a single PE-format file.
If you have only previously encountered EXEs created by a traditional linker you have led a rather sheltered existence!
Logged
