This is the mail archive of the java@gcc.gnu.org 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]
Other format:	[Raw text]

Re: buffer flushing?

From: Tom Tromey <tromey at redhat dot com>
To: Adam Megacz <gcj at lists dot megacz dot com>
Cc: Andrew Haley <aph at cambridge dot redhat dot com>, java at gcc dot gnu dot org
Date: 31 May 2002 16:17:58 -0600
Subject: Re: buffer flushing?
References: <86znyllyrg.fsf@megacz.com> <3CF3004C.4090607@waitaki.otago.ac.nz> <868z64fdod.fsf@megacz.com> <15603.48465.785312.850488@cuddles.cambridge.redhat.com> <86g00cdtdp.fsf@megacz.com>
Reply-to: tromey at redhat dot com

>>>>> "Adam" == Adam Megacz <gcj@lists.megacz.com> writes:

Andrew> Is it not possible to open the file with a mode that stops
Andrew> this from happening?

Adam> Yes, although unfortunately Sun's JDK (1.4) does not do this. So
Adam> it's probably a bad idea for libgcj to do it. Argh.

I think it would be fine for us to do this, if it is what we want.
Java programs shouldn't be relying on this behavior.  Are there other
tradeoffs?  For instance, does doing this cause strange behavior in
other situations?

Tom

References:
- buffer flushing?
  - From: Adam Megacz
- Re: buffer flushing?
  - From: Bryce McKinlay
- Re: buffer flushing?
  - From: Adam Megacz
- Re: buffer flushing?
  - From: Andrew Haley
- Re: buffer flushing?
  - From: Adam Megacz

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