From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed1.bredband.com!bredband!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: My guide to Lisp Date: 24 Aug 2002 02:41:10 +0000 Organization: Naggum Software, Oslo, Norway Lines: 21 Message-ID: <3239145670302676@naggum.no> References: <3D64F205.13C55ED6@cs.uni-bonn.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1030156870 3234 129.240.64.16 (24 Aug 2002 02:41:10 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 24 Aug 2002 02:41:10 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:38645 * Christopher Browne | In Lisp, reader macros are part of the 'base language,' | http://www.cs.utsa.edu/research/AI/cltl/clm/node188.html, allowing you to | integrate extensions in, and, if you define your own custom *READTABLE*, | allowing you to build your own language parser. I think it is important to be aware that the syntax of Common Lisp is programmable and that the value of `*readtable*ยด is not just some potentially extended syntax, it /is/ the syntax in which code is read. There is in fact no way to get around reader macros. ( invokes a reader macro. | In practice, it is usually used to provide relatively minor extensions. No, it is used to define the syntax of Common Lisp. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.