From ... From: Erik Naggum Subject: Re: Dangling Closing Parentheses vs. Stacked Closing Parentheses Date: 2000/03/29 Message-ID: <3163278794398146@naggum.no>#1/1 X-Deja-AN: 603656585 References: <38DBE821.F64C2B22@genworks.com> <8bneig$6s8$4@ssauraaa-i-1.production.compuserve.com> <86r9cwf2ec.fsf@g.local> <4u2hrgif8.fsf@beta.franz.com> <8bqukn$rtr$1@news.gte.com> mail-copies-to: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: newsmaster@eunet.no X-Trace: oslo-nntp.eunet.no 954291638 16798 195.0.192.66 (29 Mar 2000 01:00:38 GMT) Organization: Naggum Software; vox: +47 8800 8879; fax: +47 8800 8601; http://www.naggum.no User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5 Mime-Version: 1.0 NNTP-Posting-Date: 29 Mar 2000 01:00:38 GMT Newsgroups: comp.lang.lisp * Dorai Sitaram | Well, the CLISP pretty-printer gives this "semi-dangled" output: : | But if you look closer, you will realize with a jolt that the lparen that | an rparen lines up with is _not_ its matching lparen... someone recently said (sorry, I have been skimming news lately) that he had a problem starting with Lisp because everything was in uppercase -- small things like that can effectively block one's entry into new areas. back when I was fairly new to Lisp (eons and eons ago, of course), I came across CLISP and its unfingbelievably braindamaged pretty printer. it was immediately obvious that this had been implemented in a vacuum, free from influence from all knowledgable programmers on the planet and beyond, and it still sucked. to see code printed like this was such a horrible experience I immediately seized upon the source code to try to find out how to turn this gut-wrenching abomination off. but what did I find? the entire source code was formatted like this! aaaaauuugh! and everything in German, to boot. the abyss was staring back at me. CLISP has since improved. no animals have been hurt in its production. #:Erik