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!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Common syntax [was: newbie in deep over his head] References: <3223908767189370@naggum.net> <3223978900680608@naggum.net> <87zo1s1dhf.fsf@xs4all.nl> Mail-Copies-To: never From: Erik Naggum Message-ID: <3224000946175910@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: Fri, 01 Mar 2002 19:49:00 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1015012140 193.71.199.50 (Fri, 01 Mar 2002 20:49:00 MET) NNTP-Posting-Date: Fri, 01 Mar 2002 20:49:00 MET Xref: archiver1.google.com comp.lang.lisp:27672 * "Glenn Burnside" | But obviously a little sugar is good - else why '#... for function, or ' | for list? One of the things I hope you will appreciate here is that people take some pains to be as precise as they can when they post, and that means that '# instead of #' is an annoyance. ' does not mean list, it means quote. 'x does _not_ do the same as (list x), but (quote x). | Do you think you could get by without that? You mean would I abstain from defining them if I wanted them? No. :) | What if you had a Lisp environment that let you elevate the read macro | kind of thing into the editor - where the editor let you specify how you | want to view and type certain things, but the source file stored the | actual forms? Would that be worth anything? If you are not familiar with Emacs, yet, now is a good time to start. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.