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,e55245590c829bef X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!feeder.news-service.com!news.netcologne.de!newsfeed-fusi2.netcologne.de!newsfeed.straub-nv.de!diablo2.news.osn.de!news.osn.de!diablo2.news.osn.de!news.belwue.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Sat, 06 Nov 2010 20:24:08 +0100 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Beginners question: Compound types, how-to? References: <86wroy58ff.fsf@gareth.avalon.lan> <86pqup5xfy.fsf@gareth.avalon.lan> <86y69d3rec.fsf@gareth.avalon.lan> <4cd19583$0$6977$9b4e6d93@newsspool4.arcor-online.net> <82oca54q8a.fsf@stephe-leake.org> <4cd28655$0$7657$9b4e6d93@newsspool1.arcor-online.net> <82y696z95e.fsf@stephe-leake.org> In-Reply-To: <82y696z95e.fsf@stephe-leake.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4cd5ab58$0$6987$9b4e6d93@newsspool4.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 06 Nov 2010 20:24:08 CET NNTP-Posting-Host: fd00c969.newsspool4.arcor-online.net X-Trace: DXC=ejV8> On 11/6/10 5:53 PM, Stephen Leake wrote: > If a clear, simple, consistent naming convention is used, these problems > do not arise. A simple, consistent naming convention may simply not exist when you work across (a) languages, (b) on different projects... > Please stop putting up straw man arguments! ... hence the argument is not at all a straw man. Is is a simple observation of programming realities (a) and (b). What I see here is an attempt to generalize a special case. By sheer luck, some here on c.l.ada seem to be working in places where there is one established coding convention. This sure makes for a happy living on a coding island and when this island has sufficient extent, fine. But in the light of (a) and (b) above, it does not make for a general argument in favor of a convention in place of good names.