This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: java.net: Classpath vs. libgcj Comparison

To: Jeff Sturm <jsturm at sigma6 dot com>
Subject: Re: java.net: Classpath vs. libgcj Comparison
From: Tom Tromey <tromey at cygnus dot com>
Date: Mon, 17 Apr 2000 23:35:12 -0700 (PDT)
Cc: green at cygnus dot com, per at bothner dot com, java-discuss at sourceware dot cygnus dot com, arenn at urbanophile dot com
References: <200004170142.SAA07217@hoser.cygnus.com><m2vh1htq5q.fsf@kelso.bothner.com><38FA829B.69CBA01F@sigma6.com><200004170350.UAA07372@hoser.cygnus.com><38FA90AD.70BE8C26@sigma6.com>

>>>>> "Jeff" == Jeff Sturm <jsturm@sigma6.com> writes:

Jeff> Also, java.net.SocketInputStream and SocketOutputStream are
Jeff> classes I was going to propose for libgcj, since the current
Jeff> assumption that sockets can be represented by FileDescriptors
Jeff> just isn't portable (win32 at least has a completely separate
Jeff> API for socket I/O).

It seems like we'd have to hide this underneath FileDescriptor.
E.g., add a flag and have the Windows implementation switch calls at
runtime.

Tom

Follow-Ups:
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Jeff Sturm
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Bryce McKinlay

References:
- java.net: Classpath vs. libgcj Comparison
  - From: Anthony Green
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Per Bothner
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Jeff Sturm
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Anthony Green
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Jeff Sturm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]