Am 01.04.2013 um 17:38 schrieb Wolfgang Lenerz: > L >> Turbo cannot choose the dataspace which might be needed in a program it is >> compiling. > >> You can either choose a specific dataspace on compilation or increase it >> after compilation. > > From within my (basic or compiled) program? > > If not, Turbo would be unsuitable for what I'd want to achieve. > > >> >> Yes. Turbo won't compile a program unless the program resides, tokenised, in >> the master basic area. > Ah OK. Can't it handle Qsaved progs? >
All, as always in the Turbo/QLib discussions, there doesn't seem to be much difference technically, but rather in terminology. QLib uses two passes on in-memory programs. The first creates a so-called work file that contains an intermediate, tokenized and parsed form of the program (which "incidentally" uses the same file format that QSAVE uses), the second pass actually generates the object code. Turbo does the very same thing, in my understanding - just with two different executables - parser_task and codegen_task, and the "intermediate file format" is not QSAVE, but something different - which is not officially documented. If you use such a file as input for codegen_task, Turbo can very well "compile from a file". Can't actually see big differences here. Regards, Tobias _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
