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? | So the files need to be available at runtime but are not normally | used except by developers so they are autoloaded. I know, I know. Please, put aside for a moment that "modifying Axiom is hard", and walk me trough a chain of events that would led to translation (asked by user) without going through parsing. | > | This is why I say it is much harder to change axiom than it appears. | > | > Please, that is tiresome and not helpful. | | and also true. every line of code in axiom was written for a reason. Oh, I would not have guessed ;-) -- Gaby _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer