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,15890893c0618a8a X-Google-Attributes: gid103376,public From: bobduff@world.std.com (Robert A Duff) Subject: Re: [Q] Tools for Ada Quality and Style [LONG] Date: 1996/05/02 Message-ID: #1/1 X-Deja-AN: 152621993 references: <9604172134.AA27114@eight-ball> <4xwx2w8dn5.fsf_-_@leibniz.enst-bretagne.fr> organization: The World Public Access UNIX, Brookline, MA newsgroups: comp.lang.ada Date: 1996-05-02T00:00:00+00:00 List-Id: In article , Robert Dewar wrote: >...They are partially written up in >an internal document, and could be further documented, although there is >always the last epsilon where the style rules ultimately say "lay things >out in an elegant style", where it is hard to pin down the last >..details. What we call "style" ranges from little formatting issues (like how many spaces to put after a parenthesis), to vague rules like "use meaningful variable names". A person writing a novel wouldn't even consider the first one to be called "style"; that person would call it "typography", and, in most cases, would let some publisher worry about it. For the small, automatable issues, I'd rather have a tool that fixes it for me silently, rather than complaining to me. >It would be nice to have full documentation of the GNAT style. This is on >the list of things to do. Yes, it would be nice. But my earlier post exagerated (I *said* I was playing Devil's Advocate). In practise, it's not so hard to pick up most of the gnat style simply by reading the existing gnat sources. - Bob