Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Kelsey Bjarnason <kbjarnason@gmail.com>
Newsgroups: comp.os.linux.advocacy,comp.os.linux.embedded
Subject: Re: Reading the Riot Act To ARM's developers
Date: Fri, 10 Feb 2012 21:25:46 -0800
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <qnah09-1p2.ln1@spankydtr.localhost.net>
References: <WGiYq.100467$WX2.28685@newsfe28.ams2> <02c9e013-9c6b-4270-8b82-c7d16b51269c@sw7g2000pbc.googlegroups.com> <h3AYq.25807$ZT6.970@newsfe23.ams2>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Info: mx04.eternal-september.org; posting-host="1slvsP1WECuGs7FJVcqjxw"; logging-data="12646"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+XkIkkbYd1ROuSj5pJ+uUjmTgraZyfMog="
User-Agent: Pan/0.133 (House of Butterflies)
Cancel-Lock: sha1:5653L1duRfStQz9ojqjt3yzBrQU=
Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.advocacy:88133 comp.os.linux.embedded:98

[snips]

On Wed, 08 Feb 2012 19:29:52 +0000, 7 wrote:

> If I use my own names for the flags by imposing similar structures to
> that of PIC compiler, that code will not be compatible with other
> engineers who will use completely different names for the same flags.

Which matters if you're re-compiling/assembling their sources... in which 
case you can pre-process their code to use your naming (or vice-versa).  

And if they're working on the same codebase, why aren't you sharing a 
mutually-agreeable set of include files with common definitions, or some 
equivalent?

If you're not working on the same codebase, why does it matter if the 
names differ?