From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!193.251.151.101!opentransit.net!proxad.net!teaser.fr!news1.carrier1.net!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: newbie asks: why CL rather than scheme? References: <_wrT7.3347$_3.12614@news.iol.ie> Mail-Copies-To: never From: Erik Naggum Message-ID: <3217820340261235@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Dec 2001 06:59:02 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader3.kpnqwest.net 1008831542 193.71.66.49 (Thu, 20 Dec 2001 07:59:02 MET) NNTP-Posting-Date: Thu, 20 Dec 2001 07:59:02 MET Xref: archiver1.google.com comp.lang.lisp:22828 * Nils Goesche | I think there is no Lisp analogy for stuff like | | (*(int *) p)++; | | so maybe there is... Well, instead of using the pointer itself, use an index to obtain the equivalent result in Allegro CL: (sys:memref p :signed-long32) But you have to know the size of the object you have retrieved to increment the index enough. (incf 4) would work here. is somewhat magic. :signed-long32 is a fairly non-CL way of saying (signed-byte 32). /// -- The past is not more important than the future, despite what your culture has taught you. Your future observations, conclusions, and beliefs are more important to you than those in your past ever will be. The world is changing so fast the balance between the past and the future has shifted.