RFC: Moving native code in java.net into architecture dependant files

[Andrew Haley]

Michael Koch writes:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 > 
 > Am Sonntag, 16. März 2003 04:28 schrieb Mohan Embar:
 > > Michael,
 > >
 > > >Here is a patch which moves the native code of java.net into
 > > >architecture dependant files for better/easier maintaining, as
 > > >requested by several people.
 > >
 > > - Is it a done deal that all eCos variants will never have any net
 > > code in them?

No, it isn't.

 > > If not, the naming conventions seem to establish the equivalence
 > > between the eCos platform and java.net functionality being
 > > disabled. Is this confusing from a naming standpoint? What if
 > > instead of natInetAddressEcos.cc (for example), you had
 > > natInetAddressNoNet.cc and made another variable called
 > > NET_PLATFORM which factored in not only PLATFORM, but also
 > > whether enable_java_net was "no"?
 > 
 > As I understood it Ecos is more used as a synomynon for a 
 > non-supported architecture. At least I think I read that on the lists 
 > (a comment from Tom I think).

For the time being, yes.  But if someone submits a patch that properly
enables networking on eCos it'll be welcome.

Andrew.