Re: repo layout again

2006-01-04 Thread [EMAIL PROTECTED]
-Original Message- >From: George Harley1 <[EMAIL PROTECTED]> >Sent: Jan 4, 2006 12:30 PM >To: harmony-dev >Subject: Re: repo layout again > >Hi Dan, > >>Maybe I am missing something, but why should the Java compiler care >>about whether or not something is native or not? That is, why sh

Re: repo layout again

2006-01-04 Thread [EMAIL PROTECTED]
-Original Message- >From: "David N. Welton" <[EMAIL PROTECTED]> >Sent: Jan 4, 2006 11:59 AM >To: harmony-dev@incubator.apache.org >Subject: Re: repo layout again > >[EMAIL PROTECTED] wrote: > >> Better yet, keep the three variables independent because the >> _same_ chip can operate in bot

Re: repo layout again

2006-01-04 Thread George Harley1
Hi Dan, >Maybe I am missing something, but why should the Java compiler care >about whether or not something is native or not? That is, why should I >care about a stub implementation? I can't connect this to my real >implementation because it would not get routed to JNI at runtime. >(Or am I sti

Re: repo layout again

2006-01-04 Thread David N. Welton
[EMAIL PROTECTED] wrote: > Better yet, keep the three variables independent because the > _same_ chip can operate in both a 32-bit and a 64-bit modes. No idea if this needs to be taken into consideration, but some chips can also be little endian or big endian. -- David N. Welton - http://www.de

Re: repo layout again

2006-01-04 Thread [EMAIL PROTECTED]
-Original Message- >From: Tim Ellison <[EMAIL PROTECTED]> >Sent: Jan 4, 2006 6:46 AM >To: harmony-dev@incubator.apache.org >Subject: Re: repo layout again > >[EMAIL PROTECTED] wrote: >> >> Some more platform tree names: >> >> solaris32.sparc solaris64.sparc >> linux32.sparc linu

Re: repo layout again

2006-01-04 Thread [EMAIL PROTECTED]
-Original Message- >From: George Harley1 <[EMAIL PROTECTED]> >Sent: Jan 4, 2006 5:45 AM >To: harmony-dev >Subject: Re: repo layout again > >Hi Dan, > >By "the java.lang.*/java.io.*/etc. classes that have key native methods >tied to the VM" you mean the set of classes labelled as "kerne

Re: repo layout again

2006-01-04 Thread Tim Ellison
[EMAIL PROTECTED] wrote: > > Some more platform tree names: > > solaris32.sparc solaris64.sparc > linux32.sparc linux64.sparc > darwin32.ppc (Is this correct for the new MAC boxes?) Wouldn't the wordsize be better associated with the processor family? So solaris.sparc32, windows.x8

Re: #harmony on freenode

2006-01-04 Thread Leo Simons
Freenode has previously requested that we prefix channel names, so eg that we se #asfharmony (like there's #asfinfra, #asfmembers, ...). I think there's as many projects that follow that policy as there are that don't. - LSD On Fri, Dec 30, 2005 at 10:09:56AM -0800, John wrote: > I'm going to re

Re: repo layout again

2006-01-04 Thread George Harley1
Hi Dan, By "the java.lang.*/java.io.*/etc. classes that have key native methods tied to the VM" you mean the set of classes labelled as "kernel classes" in HARMONY-14. The existing documentation for these classes (see http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/harmony/enhanced/clas