This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: PATCH: remove all traces of java.io.FileDescriptor from java.net
- From: Tom Tromey <tromey at redhat dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>, java-patches at gcc dot gnu dot org
- Date: 25 Mar 2002 22:21:48 -0700
- Subject: Re: PATCH: remove all traces of java.io.FileDescriptor from java.net
- References: <Pine.LNX.4.10.10203251931040.1029-100000@mars.deadcafe.org>
- Reply-to: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
Jeff> So my inclination is to resubmit the patch minus the SocketImpl
Jeff> changes.
Is the idea that the SocketImpl.getFileDescriptor would just return
null? That seems reasonable, weirdly enough. Or maybe we could have
it either return an invalid fd or throw some exception.
There's actually two uses for getFileDescriptor; you can call
FileDescriptor.sync or FileDescriptor.valid. I don't find either of
these really compelling.
Tom