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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,8143b93889fe9472 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.180.82.1 with SMTP id e1mr2323048wiy.1.1359625894771; Thu, 31 Jan 2013 01:51:34 -0800 (PST) Path: i11ni30881wiw.0!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!192.71.180.34.MISMATCH!newsfeed1.swip.net!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Ada standard and maximum line lengths Date: Thu, 31 Jan 2013 09:51:33 +0000 Organization: A noiseless patient Spider Message-ID: References: <8dfcf819-e1d0-4578-a795-a4bf724b5014@googlegroups.com> <5107b329$0$6556$9b4e6d93@newsspool4.arcor-online.net> <5107eaed$0$6566$9b4e6d93@newsspool4.arcor-online.net> <51080c38$0$6561$9b4e6d93@newsspool4.arcor-online.net> <51085776$0$6637$9b4e6d93@newsspool2.arcor-online.net> Mime-Version: 1.0 Injection-Info: mx04.eternal-september.org; posting-host="c8da4aa61d590a5e477a2e03e552a940"; logging-data="9871"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18NkIHzmuW5x9z79+RxqpTSF/QHUuyKe7c=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (darwin) Cancel-Lock: sha1:YFVULchx1RtTAvVIjzwpf/G1snQ= sha1:vKZl+LRkPrlDjs0QN4u7VuHIIhg= Content-Type: text/plain Date: 2013-01-31T09:51:33+00:00 List-Id: Niklas Holsti writes: > In practice, when one is developing a program that generates > source-code (in Ada or other languages), it is often necessary to look > at the output to check that it is correct, or to understand why it is > wrong, and this is much easier if the output is not only broken into > lines, but also indented in the usual way. I adopted the rule that, within reasonable bounds (eg, no user-defined identifiers > 50 characters, say) the generated code shouldn't raise any style check warnings. And should act as an example of the code style desired for the hand-written code.