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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8811b64ee948c3e3 X-Google-Attributes: gid103376,public From: Dave Smith Subject: Re: Code Formatters Date: 1996/11/06 Message-ID: <55q621$v6s@gcsin3.geccs.gecm.com>#1/1 X-Deja-AN: 194872520 references: <552nkb$u1k@gcsin3.geccs.gecm.com> <327A17CA.6B30@gsfc.nasa.gov> <1996Nov5.144945.1@eisner> content-type: text/plain; charset=us-ascii organization: GEC-Marconi Combat Systems mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 1.2 (Windows; I; 16bit) Date: 1996-11-06T00:00:00+00:00 List-Id: As I seem to have started off a good old fashioned discussion on the rights and wrongs of standards formats, let me add another tw'pence worth. Surely what we need are decent development environments with good language sensitive editors. These should be able to read a file containing the "rules" to be used for layout, the indenting, capitalization, etc. being done as the code is typed in. Or maybe it would have been useful to have included the Ada Style Guide (the "bible" as far as I am concerned) as part of the ANSI standard. Them we would all have code that conformed to the same layout. To me, the reasons for having a standard layout are: 1) Coders don't need to think how to layout the code, and so can get on with the coding. 2) It's easier to read someone else`s code. 3) Having a standard layout makes it easier to give the code listings to the customer. The last thing I want to do is to send a customer the listings for ten packages all using a different style. BTW Thanks to Robert Dewar for getting involved in this thread... "We are not worthy!" Dave Smith Chief Software Engineer GEC-Marconi S3I Combat Systems Division Addlestone England