Re: [Axiom-developer] Error when converting to a set

[Camm Maguire]

Greetings!

root <address@hidden> writes:

> Yes, the issue still exists. I know that it fails due to a length
> computation somewhere in the Charybdis subsystem (Axiom's printing).
> I have not yet found the offending bit of lisp code but I'll retry
> the example after this new build completes and see if I can isolate it.
> 

Thanks.  Please let me know.  To my knowledge this is the only
remaining axiom build issue which has been shown to vary with the
underlying lisp, correct?  I just checked, and we have no known bugs
in our ansi-test suite relating to the set functions, other than the
type of error reported.  You may have found something new, or it may
be an ordering issue as you've implied earlier.

Take care,

> I've applied your stack patch and will also test it after this build 
> completes.
> 
> > Greetings!  Does this issue persist?  If so, can it be boiled down to
> > a simple lisp example?
> > 
> > Take care,
> > 
> > "Juergen Weiss" <address@hidden> writes:
> > 
> > > The last command in coercels.input converts the result
> > > to a set. With gcl, the result contains duplicate 
> > > elements. Problem does not occur with cmu cl.
> > > 
> > > Juergen Weiss
> > > 
> > > Juergen Weiss       | Universitaet Mainz, Zentrum fuer Datenverarbeitung,
> > > address@hidden| 55099 Mainz, Tel: +49(6131)39-26361, FAX:
> > > +49(6131)39-26407
> 
> Tim
> address@hidden
> address@hidden
> 
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah