From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f2125390ce17553a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-11-14 07:46:28 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!uio.no!newsfeed.song.fi!newsfeed.kolumbus.fi!not-for-mail From: Martti Halminen Newsgroups: comp.lang.ada Subject: Re: I want to ask you All an advice, please Date: Thu, 14 Nov 2002 17:30:34 +0200 Organization: Elisa Internet customer Message-ID: <3DD3C19A.C0DAD898@kolumbus.fi> References: <3dd10fa0_2@news.arcor-ip.de> <3DD11253.7050102@nestcape.net> <3dd2147f_1@news.arcor-ip.de> NNTP-Posting-Host: ui115i20hel.dial.kolumbus.fi Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: phys-news1.kolumbus.fi 1037288784 14372 62.248.189.115 (14 Nov 2002 15:46:24 GMT) X-Complaints-To: abuse@kolumbus.fi NNTP-Posting-Date: Thu, 14 Nov 2002 15:46:24 +0000 (UTC) X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.10-4GB i686) X-Accept-Language: en Xref: archiver1.google.com comp.lang.ada:30878 Date: 2002-11-14T17:30:34+02:00 List-Id: Georg Bauhaus wrote: > > In comp.lang.ada Fred Gilham wrote: > > : o simple syntax[2] > > If you can't accept that this may be considered syntax (also), > then consider that "human stacks" are pretty bad in bracket > matching. After all there is a reason that we write many small functions > and not a few big ones. I believe that too many ()s will make you crazy > and not very productive. What makes you think that it would be any different in Lisp? In my programs the average size of a lisp function is less than 15 lines. > How many levels of nested function application can a human being > remember? Try > (+ 3 (* 4 (+ 7 6 (- 5 1)) (/ 4 (+ 5 6))) > "by hand" for an easy example. The tree isn't unusually high. Few Lisp programmers would write it like that. (+ 3 (* 4 (+ 7 6 (- 5 1)) (/ 4 (+ 5 6)))) would be more likely to be found in actual code. The trick in reading Lisp is to leave the bellyaching about parentheses to the compiler and editor, and use the indentation to read the code structure. --