> [Original Message]
> From: Etienne Gagnon <[EMAIL PROTECTED]>
> To: <harmony-dev@incubator.apache.org>
> Date: 3/30/06 6:39:47 AM
> Subject: Re: [classlib] ant platform property definitions
>
> Isn't there some "standard" naming strategy, used by other Apache
> projects? I know that autoconf has a platform naming strategy.
>
> I recommend to study other platform naming strategies before making a
> decision. This will help reduce the number of mistakes.
>
> Etienne
>
Especially mistakes when working between different areas of the
Harmony project where different conventions are used! The earlier
we come up with a project-wide convention, the easier it will be in
the long run. I'm open to ideas, but let us stick to single-case tokens
that keep OS, CPU, and word width separate, but which can mix
and match them into derived tokens as needed.
Dan Lydick
> bootjvm wrote:
> > Bottom line: Mixed case just adds one more level of complexity
> > to the whole situation. Other comments below....
> >
> >
> > OS names:
> > linux
> > cygwin
> > windows
> > solaris
> >
> > CPU names:
> > intel
> > sparc
> > ppc
> >
> > Word widths:
> > 64
> > 32
>
> --
> Etienne M. Gagnon, Ph.D. http://www.info2.uqam.ca/~egagnon/
> SableVM: http://www.sablevm.org/
> SableCC: http://www.sablecc.org/
