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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,429176cb92b1b825 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 Path: g2news2.google.com!news4.google.com!feeder.news-service.com!94.75.214.39.MISMATCH!aioe.org!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: AWS Coding Styles (and about boring plain-linear text files in the end) Date: Tue, 18 Jan 2011 08:26:03 +0100 Organization: Ada @ Home Message-ID: References: <3077fffa-eed7-4763-8bca-9ac3bb0a41e1@o14g2000prn.googlegroups.com> <4D353B22.2090901@obry.net> NNTP-Posting-Host: IbwjOtp6CRWK4RAOHu6GbA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 User-Agent: Opera Mail/11.00 (Win32) Xref: g2news2.google.com comp.lang.ada:17480 Date: 2011-01-18T08:26:03+01:00 List-Id: Le Tue, 18 Jan 2011 08:02:58 +0100, Pascal Obry a =C3=A9= crit: >> Then again, I've never had much use for style guides, especially when= >> they're enforced. I think I do a good job of being sensitive to >> others who might read my source, and writing in a way that makes it >> easier on them; sometimes strict rules can actually prevent me from >> doing the best job of this, especially since the one who writes the >> rules may not have thought about every possible circumstance. > > In contrary, I do like very much style guide for at least one reason. > When you work in with a group of developer no one should own somehow a= > bit of code. A uniform indentation avoids : "this is my code", "this i= s > joe part"... Everybody on the team should feel comfortable with the > whole software. The style is not that important, but a single style > across a project is if you ask me. Good points and well justified (will note it in my mind). And on my side, I feel guide-lines documentations comes as natural with = = design documentation (as part of it). It is also one of the easiest to = start with when you at least want to give a seed to such documentation. = = This may also be a sign the author(s) cared ;) If I was to rate projects= , = this would be a constant criteria and I would give or retain some points= = based on the presence or absence of such documentation. -- = Si les chats miaulent et font autant de vocalises bizarres, c=E2=80=99es= t pas pour = les chiens. =E2=80=9CI am fluent in ASCII=E2=80=9D [Warren 2010]