Re: Announcing a new release of Lisp1 #2
- From: "Kjetil S. Matheussen" <k.s.matheussen@xxxxxxxxxx>
- Date: Wed, 30 Jan 2008 17:29:05 +0100
(removed comp.lang.scheme, only relevant to comp.lang.lisp)
On Wed, 30 Jan 2008, Blake McBride wrote:
I would further add that Scheme should define argument evaluation order.
Compilers can be written to support a particular order just as well as
another order. This is no argument for unspecified argument evaluations
order. Having the argument evaluation order unspecified is a huge and
totally unnecessary opportunity for porting bugs.
Scheme is not haskell, so I agree about that.
BTW, does common lisp specify the order of arguments?
.
- Follow-Ups:
- Re: Announcing a new release of Lisp1 #2
- From: Rainer Joswig
- Re: Announcing a new release of Lisp1 #2
- Prev by Date: Re: Formatting large numbers with ~g?
- Next by Date: Re: Announcing a new release of Lisp1 #2
- Previous by thread: Tail recursion syntactic sugar faked with TAGBODY-based construct?
- Next by thread: Re: Announcing a new release of Lisp1 #2
- Index(es):