Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!vtserf!creatures!csgrad!lavinus
From: lavinus@csgrad.cs.vt.edu
Newsgroups: comp.lang.lisp
Subject: Re: weird common lisp feature
Keywords: read, read-line
Message-ID: <964@creatures.cs.vt.edu>
Date: 22 Feb 91 20:47:41 GMT
References: <12413@helios.TAMU.EDU> <1991Feb21.104336.26012@Think.COM> <18935@brahms.udel.edu>
Sender: usenet@creatures.cs.vt.edu
Reply-To: lavinus@csgrad.cs.vt.edu ()
Organization: Virginia Tech Computer Science, Blacksburg, VA
Lines: 19

Yo out there...

Everyone seems to be missing a basic point of Lisp philosophy: If you do
something like (foo a) (foo2 b), you should not count on that being evaluated
left-to-right or right-to-left.  Generally, it is good programming practice
(in general, but especially in Lisp) not to make any assumptions about order
of evaluation unless the *language* (not the compiler) guarantees some
particular order (the only example I can think of offhand is C - it guarantees
order of evaluation of most everything).

So long...

Joe Lavinus

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Joseph W. Lavinus                           =     \  /      =
= Virginia Tech, Blacksburg, Virginia         =      \/__V    =
= email: lavinus@csgrad.cs.vt.edu             =      /\       =