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,429176cb92b1b825 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news2.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Tue, 18 Jan 2011 06:42:57 -0600 Date: Tue, 18 Jan 2011 07:42:55 -0500 From: "Peter C. Chapin" Organization: Vermont Technical College User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: AWS Coding Styles (and about boring plain-linear text files in the end) References: <3077fffa-eed7-4763-8bca-9ac3bb0a41e1@o14g2000prn.googlegroups.com> <4D353B22.2090901@obry.net> In-Reply-To: <4D353B22.2090901@obry.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Message-ID: X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-g2IFTtiByDrkKYI0zJo/X597V248BqGFWrTpPcU+1006ghaM9lbkj5au3MvmbmsIZ5PF0gboz2I23Y5!1ab58/Y6xc2xXUc7X5bc35dxj8giHFd8q7tLMYy8l5eDDp1sAOmSP03agjumZws= X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2472 Xref: g2news2.google.com comp.lang.ada:17490 Date: 2011-01-18T07:42:55-05:00 List-Id: On 2011-01-18 02:02, Pascal Obry wrote: > 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 is > 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. I want to echo my agreement with this. I'm working on a project with several students, most of whom are fairly inexperienced. Having a common style is very helpful. Instead of brow beating the students into a particular style we've agreed to just follow what gnatpp does. We can agree on a particular configuration of the pretty printer and then everyone can conform to the project specified style by just pressing a button in GPS. No arguments. I agree with Adam that sometimes the results are less than optimal and certainly not as good as *I* would do on my own. :) Yet having an enforced style that can be easily applied with the help of a tool has made the code base better overall. Peter