In http://wiki.axiom-developer.org/347BugInMapSet
'oklhazi' reported that "map confuses sets" and gives
the example
A:=set [-2,-1,0]
B:=set [0,1,4]
C:=map(x +-> x^2,A)
test(C=B)
where the map operation produces a "Set" C with the same
elements as B but which is not equal to B, thus viola
I have just had a look at the sources.
The redefinitions of
ASSOC, DELETE, INTERSECTION, MEMBER, RASSOC, REMOVE, UNION
seem to have the same source (all defined in vmlisp.lisp).
COMMON LISP has different semantics than VMLISP
(in this case with regard to equality in those functions).
Juergen
Quoting "Weiss, Juergen" <[EMAIL PROTECTED]>:
The replacements GET --> GETL, READ --> VMREAD indicate, that=20
they were introduced to circumvent different semantics of
GET and READ between VMLISP and COMMON LISP. Not clear=20
about the others.
Many thanks. I'll document that when I'm back to
The replacements GET --> GETL, READ --> VMREAD indicate, that
they were introduced to circumvent different semantics of
GET and READ between VMLISP and COMMON LISP. Not clear
about the others.
Regards
Juergen Weiss
Juergen Weiss | Universitaet Mainz, Zentrum fuer Datenverarbeitung,
[EMAIL
Waldek Hebisch wrote:
> I would prefer to eliminate all renaming at boot/shoe level. Instead,
> I would just define needed functions at Lisp level (partially in the
> style of unlisp.lisp.pamphlet, but also using compiler macros for
> efficiency). Also, I consider using all-lowercase Lisp (makin
>
>
> It is generally admited that in Boot (whether old or new) an
> identifier written in all uppercase is passed unmodified in the
> generated Lisp code (except for T). Right?
>
> Well, Old Boot says "Wrong!". Some of the all-uppercase identifiers
> are renamed into case-sensitive uppercase,
[EMAIL PROTECTED] wrote:
> I plan to attend ECCAD in Delaware and ISSAC in Canada. --Tim
Tim, isn't ECCAD in MD this year?
http://eccad07.washcoll.edu/
Or do I have the wrong conference?
CY
___
Axiom-developer mailing list
Axiom-developer@nongnu.or
