Re: The semicolon habit (was: Q: Definition of a scripting lang.)

Charles Fiterman <cef@geodesic.com>
Thu, 11 May 1995 12:56:47 GMT

          From comp.compilers

Related articles
[13 earlier articles]
Re: The semicolon habit (was: Q: Definition of a scripting lang.) lwall@netlabs.com (1995-05-09)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) tchannon@black.demon.co.uk (Tim Channon) (1995-05-04)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) ok@cs.rmit.edu.au (1995-05-04)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) bevan@cs.man.ac.uk (1995-05-10)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) bevan@cs.man.ac.uk (1995-05-10)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) monnier@di.epfl.ch (Stefan Monnier) (1995-05-11)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) cef@geodesic.com (Charles Fiterman) (1995-05-11)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) plong@perf.com (1995-05-11)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) stidev@gate.net (1995-05-12)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) rabin@CS.YALE.EDU (1995-05-12)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) plong@perf.com (1995-05-12)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) bevan@cs.man.ac.uk (1995-05-15)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) bevan@cs.man.ac.uk (1995-05-15)
[1 later articles]
| List of all articles for this month |
Newsgroups: comp.compilers
From: Charles Fiterman <cef@geodesic.com>
Keywords: design
Organization: Geodesic Systems
References: 95-04-013 95-05-047
Date: Thu, 11 May 1995 12:56:47 GMT

scooter@mccabe.mccabe.com (Scott Stanchfield) writes:
>On the mainframe, tabs were a non-issue. On UNIX, I think they could cause
>tons of grief.


Richard A. O'Keefe <ok@cs.rmit.edu.au> wrote:
[Don't confuse 8 char Unix tab stops with indentation levels.]


I agree absolutely. But would like to say that the TAB in data is really
a misplaced compression algorithm. If you want to compress data use compress,
or gzip, or ARC. Never put TAB characters in data, and programs are data.


BTW psychological experiment show that the most readable tab value for
programs is 3. However other values 1..8 are not bad. That right a tab
size of one in a program is not bad. Zero is very bad. So if you are
worried about some deeply indented code not having space you can use
a tab size of 1 and still be quite readable.
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.