John Gilpin wrote:
<>
Is there a reliable way of listing all the 'extras' currently loaded and
is there a way of getting a list of 'extras' each extension should load
- say from the .bin file that is being LRESPRd?. This would be useful in
determining whether an extension will overwrite a particular entry
already loaded.
There is no accurate way to determine which unique extensions will be
loaded by any given toolkit, for mainly three reasons.
1. Extensions will overwrite any previous extension with the same name
2. A toolkit may selectively load only some extensions
3. Theoretically, (but unlikely) a toolkit could generate extension
name(s) on the fly or alter the names of existing extensions!
Using a program or editor to determine which extensions will be loaded
may fail for the reasons above.
Having said that, most toolkits are pretty straightforward, so only
reason 1. above will apply.
EXTRAS in job #0 is pretty reliable, except you cannot tell which
keywords have been redefined. If you really need to know, youd have to
load one toolkit at a time, dump the keyword list using EXTRAS, reboot
and do the next. Then you could decide in which order to load the
toolkits.
Is there a recognised sequence that extensions should be loaded in? -
i.e. TK2 before Menu_rext.
Because of reason 1. given above, the order of toolkits loaded can be
significant. One toolkit's PEEKS might do something completely
different to another's. There is no general rule apart from testing to
see what works. For the main toolkits, Id follow Dilwyn's advice, for
any additional toolkits, load those that are required by the programs
most important to you last! If you end up with a heart-rending
conflict, youll have to resort to patching. But thats another topic ;o)
Is there a way of getting say "EXTRAS" loaded without loading all the
other 400+ 'keywords' contained in TK2?
Ah, but you may need TK2 for many good reasons. Invisibly to the user,
it redefines a number of existing internal keywords (such as CALL,
DIR, DELETE, and many others). TK2 contains the LRESPR keyword we all
find so useful, and it also contains many other useful non-keyword
facilities, like bug fixes for the QL ROMs (I seem to recall).
There are, however, lighter versions - and even a configurable version
- out there (Dilwyn will know)
<>
Per
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
