From ... Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!134.222.94.5!npeer.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Programming Style References: <9kpnol$b70@news.csus.edu> Mail-Copies-To: never From: Erik Naggum Message-ID: <3206226647778055@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Aug 2001 02:30:49 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: nreader1.kpnqwest.net 997237849 193.71.66.49 (Wed, 08 Aug 2001 04:30:49 MET DST) NNTP-Posting-Date: Wed, 08 Aug 2001 04:30:49 MET DST Xref: archiver1.google.com comp.lang.lisp:14151 * "Roy Mash" > One goal of programming style is to facilitate code changes. In this regard, > the C style weds function and form in a way the Lisp style does not. The C style was designed to work well with ed, the standard editor, on a teletypewriter. The style of Fortran was similarly inspired by punched cards. The style of Lisp was inspired by full-screen editors with commands to move around in expressions: up, down, forward, backward. This is just one of the large number of benefits of having a delimiter at both the beginning and end of an expression, at all levels of expression. Coming from the C language family, this will take a while to register as a feature, but once you understand, you will regard the idea that the line is the most natural division as incredibly backward, almost retarded. Despite being much older than C, the Lisp family did a large number of things right that the C/Unix folks still have not grasped the significance of. Or maybe it is _because_ it is so much older. ///