[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Axiom-developer] RE: algebra Makefiles with explicit dependencies,

From: Bill Page
Subject: RE: [Axiom-developer] RE: algebra Makefiles with explicit dependencies, bootstrap, fixed-points etc.
Date: Fri, 7 Jan 2005 10:27:21 -0500


Thanks for the quick first steps at analsis of these results.
Obviously it is going to take some time to fully understand
your approach as I learn more about Axiom internals.

I did receive your attachment because you Cc'd the message
directly to me. But as you say, the mailing list put it in
the approval queue because of the size. The message size
limit was set at 40 Kbytes, which I think is pretty small
by today's standards. I have doubled this to 80 Kbytes, so
there should be fewer cases were messages end up waiting for
moderator approval. I think 80 Kbytes is still conservative
but if anyone on the mailing list objects or would prefer a
higher limit, please let me know.

Bill Page.

On Friday, January 07, 2005 9:59 AM Stephen Wilson wrote:
> My original message was rejected my the mailing list server as being
> too large due to the archive file mentioned below. Attached is the
> original message for the benefit of the list. Bill, Tim, if you did
> not get the archive (and would like a copy :) let me know and I'll
> send it out directly (or to any one else who is interested).
> [original message]
> Bill, Tim,
> The discovery of inconsistencies as witnessed by Bill's fixedPoint.log
> has me concerned. Im interested in understanding why this is
> happening. Looking over fixedPoint.log demonstrates that most (but not
> all) of the lisp code differs w.r.t the layout of the domain
> vectors (most differences occur in lisp take the form (QREFELT $ N),
> where N is an integer). 
> To understand this better, I wrote some lisp to extract the functions
> from Bills fixedPoint.log and `explode' it into several other,
> pprinted files. Running diff on these files gives a more informative
> report on what exactly has changed in the lisp. The code which does
> this is in extract.lisp. The archive already contains the exploded
> lisp files. 
> ...

reply via email to

[Prev in Thread] Current Thread [Next in Thread]