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

bevan@cs.man.ac.uk (Stephen J Bevan)
Wed, 10 May 1995 11:12:07 GMT

          From comp.compilers

Related articles
[11 earlier articles]
Re: The semicolon habit (was: Q: Definition of a scripting lang.) daveb@perth.DIALix.oz.au (1995-04-30)
Re: The semicolon habit (was: Q: Definition of a scripting lang.) anw@maths.nottingham.ac.uk (Dr A. N. Walker) (1995-05-02)
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)
[3 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: bevan@cs.man.ac.uk (Stephen J Bevan)
Keywords: syntax, design
Organization: Department of Computer Science; University of Manchester
References: 95-04-013 95-05-013
Date: Wed, 10 May 1995 11:12:07 GMT

mitchell@mdd.comm.mot.com (Bill Mitchell) writes:
      ... I often work with source files
      which have been touched by multiple programmers. Besides introducing
      confusing style switches, everyone uses their own favorite editor.
      some editors expand tabs to blanks, some to wierd editor-specific
      combinations of tabs and blanks, and some put tabs in untouched. ...


and concludes with :-


      ... Inferring flow control from indent level just does not work in
      practice in a multi-programmer, multi-editor multi-display-format
      situation.


Wouldn't the problem be solved if all the programmers on the project
followed (and stuck to!) a style guide? I know it can grate to have
to use a style which does not match your own, but IMHO the advantages
outweigh the disadvantages on a multi-person project. Since this is
comp.compilers not comp.software-eng I'll leave it at that.
--


Post a followup to this message

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