From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc2.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: A simple quesion... References: <9qbam7$9na$1@news.seed.net.tw> <3212051527684266@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3212128554160868@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Oct 2001 09:55:55 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: nreader1.kpnqwest.net 1003139755 193.71.66.49 (Mon, 15 Oct 2001 11:55:55 MET DST) NNTP-Posting-Date: Mon, 15 Oct 2001 11:55:55 MET DST Xref: archiver1.google.com comp.lang.lisp:17846 * Kaz Kylheku | What aspects of Scheme are defined at the character level, whose Lisp | counterparts are not defined at that level? Like its Algol heritage, Scheme has been (Kent indicates that they may have fixed this) defined such that it can be processed with a regular lexer that does not operate with lists of Scheme objects. It is quite interesting to watch how languages gain complexity when their syntaxes are defined at the character level that reaches far into the higher-level constructs and how they gain it when their syntaxes are defined as the parsed representation of the lowest-level objects and the higher-level constructs of the language is instead defined in terms of those objects. /// -- The United Nations before and after the leadership of Kofi Annan are two very different organizations. The "before" United Nations did not deserve much credit and certainly not a Nobel peace prize. The "after" United Nations equally certainly does. I applaud the Nobel committee's choice.