Thanks for the idea. I can split my program up into two or more modules, and then use LINK_LOAD. Variables, procedures and functions can then be shared. This is a great idea.
Michael ________________________________ From: George Gwilt <grggw...@gmail.com> To: ql-us...@q-v-d.com Sent: Tuesday, 14 February 2012, 10:10 Subject: Re: [Ql-Users] Large turbo tasks On 13 Feb 2012, at 22:05, Tobias Fröschle wrote: > Am 13.02.2012 22:45, schrieb Dilwyn Jones: >> I'm not sure if this has changed in recent versions of Turbo, but there used >> to be a setting which allowed you to produce smaller programs by limiting >> the compiled size to 64K (word length addressing etc I suppose). There is a >> setting on the control panel (the green screen started by the CHARGE >> command) which lets you select <64K or >64K in one of the boxes. There's >> also a equivalent compiler directive which I can't remember from memory (one >> of the TURBO_nnn commands, possibly TURBO_MODEL - see Turbo Toolkit manual) >> which lets you tell the compiler which settings to use to control over the >> reduced file sizes - remember Turbo was originally conceived when we didn't >> all have as much memory on our systems as today! >> >> Dilwyn Jones >> >> -----Original Message----- From: Michael Bulford >> Sent: Monday, February 13, 2012 9:28 PM >> To: ql-us...@q-v-d.com >> Subject: [Ql-Users] Large turbo tasks >> >> I am developing a program in SuperBASIC, and compiling with Turbo. The size >> of the compiled code is around 133k at the moment but I still have quite a >> lot to add. The problem is I am getting reports of "Code too large to >> compile", etc. What I have decided to do is to remove some parts of my >> code, and down-grade the program slightly. I can also move some parts to >> another separate task, but overall this is some problem. >> >> What I was wondering is if perhaps new versions of the parser and codegen >> tasks could be produced to increase the limits to allow larger sizes to be >> compiled. It is so easy nowadays to write large programs without having to >> worry about program size or the amount of dataspace used. >> >> Michael Bulford >> _______________________________________________ >> QL-Users Mailing List >> http://www.q-v-d.demon.co.uk/smsqe.htm >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2112/4807 - Release Date: 02/13/12 >> >> _______________________________________________ >> QL-Users Mailing List >> http://www.q-v-d.demon.co.uk/smsqe.htm >> > Michael, > If you're mentioning 133k compiled, that's definitely large. > The largest SB program I know is Editor, with about 100k code size. > I guess you should also run out of line numbers shortly. > Have a look at LINK_LOAD et al - This allows you to off-load parts of your > code into external libraries. > > Cheers, > Tobias > Yes. LINK_LOAD ought to work. George _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
