RE: [Axiom-developer] Help with JET

[Bill Page]

Grégory,

Excellent! Thank you very much for finding this solution.

I was not aware that the order in which the pre-compiled modules
are listed could affect how they behave. Of course, for initial
compilation from source only certain orders are possible based
on the intermodule dependencies (at least there are no circular
dependencies here! :). But it seems like either a bug or a serious
design flaw in the way Axiom processes the )lib command that the
order here seems to matter. Do you agree that we should document
this "lib order dependency" as a bug/issue?

I wonder if this bug might also bite us if/when we try to add the
JET code into the main Axiom library?

Cheers,
Bill Page.

On February 11, 2006 6:11 PM Vanuxem Grégory wrote:
> 
> My apologies, JET does not really work on Windows nor on Linux.
> The test was just a fresh compilation of JET in the order mentioned
> in a previous email. That worked because, i think, the procedure
> (of compilation) loads the library in a special order (thanks 
> Bill for your question).
> 
> For example the janet sample from Seiler works with
> 
> )lib JBC JBFC JBC- JBFC- BFC BFC- JB JBX   JBLF  DE SEM  DIFF JBE CK
> 
> Another order trigger the evalSlotDomain bug or 
> 
>    >> System error:
>    The index, 3, is too large.
>