On 28 Jan 2011, at 12:10, Dilwyn Jones wrote: >> Plastic wrote: >> >>> Apologies for the off-topicness, but one thing I'd like to see from Turbo >>> or other compilers is a "command maker" that can take a PROCedure or >>> FuNction, compile it, and package it up so it can be loaded to extend >>> BASIC. >> >> Works with QLib (and also Turbo, I think). With QLib, if you start such a >> "resident" extension, it results in creating a JOB (even if without >> windows), so I think, not quite what you want. >> >> Cheers...Ralf > For Turbo, there is a utility called Task Commander which takes an executable > program and repackages it to make it into a keyword. As Ralf says, the file > can be LRESPR'ed but becomes a job when the keyword is called (like an EX or > EW depending on whether a comma is added to the command name). > > Task Commander is among the "Turbo Extras" package on the Turbo page of my > website or from the Scottish QL Users Group site > athttp://www.jms1.supanet.com/SQLUG/gwilt/gwiltturbo.htm > > It's a long time since I last used Task Commander, so I don't know if it > works with current versions of Turbo. Maybe George can confirm this (as he > updates Turbo nowadays).
In the file TRBOX_ZIP there are four files tascom3_xx where xx is one of 00, 01, 10, 11. These take an executable program and turn it into a file which can be LRESPRd to give the keyword you have chosen. The four values of xx set defaults. The first value is 0 for not reentrant and 1 for reentrant. The second value is 0 for not default #1 and 1 for default #1. Any of these four tascom files can be configured to one of the others. I have in fact altered PHOTON to the keyword PHOT. I find this very useful. The TASCOM set do not need TURBO for their operation. The keywords to which they give rise can, of course, be used in programs compiled by TURBO. George _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
