Xref: utzoo comp.unix.internals:2629 comp.windows.news:2580 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!barnett From: barnett@grymoire.crd.ge.com (Bruce Barnett) Newsgroups: comp.unix.internals,comp.windows.news Subject: Re: X11 bashing Message-ID: Date: 25 Apr 91 14:25:41 GMT References: <28063@uflorida.cis.ufl.EDU> > <=V6&^Q_.19037@cheers.Bungi.COM> <130080@uunet.UU.NET> <4_XAYQ1@xds13.ferranti.com> <.VYA9Y1@xds13.ferranti.com> Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.ge.com Followup-To: comp.unix.internals Organization: GE Corp. R & D, Schenectady, NY Lines: 24 In-reply-to: peter@ficc.ferranti.com's message of 24 Apr 91 22:47:37 GMT In article <.VYA9Y1@xds13.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes: > You young kids today. You're spoiled by all this memory! Watch it! I cut my programming teeth on a Intel 4004 microprocessor! >Use whitespace and comments! I know how to use whitespace and comments. But does everyone else? Sometimes white spaces are detrimental. Having the entire routine on a single page is better than putting each command on it's own line and making the code three times longer. There are advantages to the lisp syntax. At least you can parse the code without knowing each command and without REQUIRING comments to document the operand stack. Forth/PostScript has some nice points as an interactive language. I wonder if some special characters can be added to the NeWS/PostScript language using a different font that allows a programmer to insert special brackets that have no function but do allow vi/emacs and the programmers to balance the stack parameters. -- Bruce G. Barnett barnett@crdgw1.ge.com uunet!crdgw1!barnett