From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!npeer.kpnqwest.net!EU.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: what lisp can do that C can't do References: <7b8f89d6.0205220934.6a8eca1b@posting.google.com> <3CECA7CE.C001262B@uab.ericsson.se> <558H8.37514$Ka.2775665@news2.calgary.shaw.ca> <3CEDF326.318319FE@uab.ericsson.se> <864rgy53jw.fsf@raw.grenland.fast.no> <3CEE0750.4BEABDC1@uab.ericsson.se> <3CEE15DF.EE8C7694@uab.ericsson.se> Mail-Copies-To: never From: Erik Naggum Message-ID: <3231229123051721@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 15 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 May 2002 11:38:45 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1022240325 193.71.199.50 (Fri, 24 May 2002 13:38:45 MET DST) NNTP-Posting-Date: Fri, 24 May 2002 13:38:45 MET DST Xref: archiver1.google.com comp.lang.lisp:33818 * Barry Watson | I don't think you're thinking "big " enough. Just because something is | standardised in a language doesn't mean it cannot be done in another | language. I'm not criticising the way it is done in Lisp. I'm just | pointing out it is doable in C. That's all. Relaxez vous! I think you have shown us something interesting. You think Common Lisp only offers what you can do in C, so naturally you can do in C what you think Common Lisp offers. This is not quite the same as doing in C what Common Lisp offers to a Common Lisp programmer. -- 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. 70 percent of American adults do not understand the scientific process.