Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of oliver.deakin@googlemail.com
 designates 64.233.184.232 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=googlemail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=N1Gktug6zliyao1wqgMMdyE1V3e17lH+v9BVOS8zeDzdNk9W480rREuWdXwAmWvL7AmhnxDo29F9eD0OhLfBoZktMCA4tuJ47ml0AwD77cxSNW/h+UxE+o87Q0QCjnua+Nj52Doy27TmXhuNt1fkIoHB5diAm93WhbsWtEohOdI=
Message-ID: <442B9DAE.30503@googlemail.com>
Date: Thu, 30 Mar 2006 09:58:22 +0100
From: Oliver Deakin <oliver.deakin@googlemail.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib] ant platform property definitions
References: <410-22006343021526990@earthlink.net>
 <fcb9f9160603292154o18b33f09raac47f1a416c1858@mail.gmail.com>
In-Reply-To: <fcb9f9160603292154o18b33f09raac47f1a416c1858@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Mark Hindess wrote:
> Dan,
>
> Thanks for the helpful comments.
>
> On 3/30/06, bootjvm <bootjvm@earthlink.net> wrote:
>   
>> Concerning the ideas for platform names, I think lower case names
>> like 'linux' and 'windows' and 'solaris' and 'aix' is by far the simplest
>> method.  It avoids UPPER case errors with the shift key for these
>> _very_ common key sequences, reducing "Inaccurate kEy SEquences"
>> quite a bit.  I have seen this work well for both platform names
>> and for project names (such as "newproj1" instead of "NewProj1")
>> with favorable long-term response from those who type the key
>> sequences most.
>>     
>
> Very good point.  You are absolutely correct.  Sticking with Ant case
> may reduce complexity in the ant files but it makes things more
> confusing/complex for users.  This would be a bad idea.  The case
> mapping can be managed in a single ant file, for classlib anyway,
> which should make it manageable.
>   

Agreed. Using mixed case just adds potential for errors. All lower case 
is simple and doesnt
require us to remember whether, for example, aix is "AIX" or "Aix" or 
whatever.

>   
>> Bottom line:    Mixed case just adds one more level of complexity
>> to the whole situation.  Other comments below....
>>
>> Dan Lydick
>>
>>
>>     
>>> [Original Message]
>>> From: Mark Hindess <mark.hindess@googlemail.com>
>>> To: Harmony Dev <harmony-dev@incubator.apache.org>
>>> Date: 3/29/06 10:28:41 AM
>>> Subject: [classlib] ant platform property definitions
>>>
>>> Currently a number of the classlib ant files "normalize" operating
>>> system and architecture names.  Unfortunately they don't
>>> really normalize them in the same way.  ;-)
>>>
>>> For instance, native-src/build.xml sets target.platform to
>>> "linux.IA32" and modules/security/make/build.xml sets "platform.name"
>>> to "lnx".
>>>
>>>       
>> PLEASE, no abbreviations!  Nobody abbreviates the same way, and
>> even one individual may use more than one abbreviation for a word!
>>     
>
> Agreed.
>   

Seconded. Again, abbreviations are something that will add complexity 
and opportunity for errors.


-- 
Oliver Deakin
IBM United Kingdom Limited