Waldek Hebisch <[EMAIL PROTECTED]> writes:
| > root <[EMAIL PROTECTED]> writes:
| >
| > | > | It turns out that (see lines 152, 154of the build-interpsys function
| > | > | in util.lisp) there are lists of functions which will trigger
| > | > | autoloading of files for a specific purpose.
| > | >
| > | > translation comes after parsing, which already autoloaded def.lisp.
| > | >
| > | > What am I missing?
| > |
| > | You're missing the fact that translation can occur at runtime long
| > | after the build system is gone.
| >
| > Which "build system"?
| >
| > The translation I'm talking about is the one that happens when the
| > system is *used*, i.e. fed with a SPAD file by user. To get that
| > translation done, the parser must have been (auto)loaded. No?
| >
| > | This can be done by user commands.
| >
| > I know; that is what I'm talking about.
| >
| > How can the translation happen without a prior parsing?
| >
|
| In principle "user" can type-in parse tree by hand and call the translator.
| More realistically, one can add code which directly generates Spad like
| parse trees and then calls translator to output Aldor.
That is a good point, though as you mentioned, it is unlikely to
happen because the parse tree is undocumented and virtually nobody
knows how to construct them by "hand"
My removal was based on the observation that translation
cannot happen without parsing. However, I'll restore the load on the
premise that translation can theoretically happen without parsing,
even if in practice, that is not going to happen.
Notice, that the removal was not based on the observation that the
file name appears twice or that something appears unused.
| ATM both are very unlikely to happen, but hardcoding in translator
| dependence on parser looks bad.
agreed in principle; however notice
if translateOldToNew then
oldParserAutoloadOnceTrigger() -- this load def.lisp
browserAutoloadOnceTrigger()
spad2AsTranslatorAutoloadOnceTrigger()
sayKeyedMsg("S2IZ0085", nil)
convertSpadToAsFile path
The function |tr| from util.lisp appears to be in the air, along with
"tr" from wi1.boot.
-- Gaby
_______________________________________________
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
