X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f Date: Mon, 11 Apr 2005 23:05:06 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp-workers AT delorie DOT com Message-ID: <01c53ed1$Blat.v2.4$e698fcc0@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: emacs 22.0.50 (via feedmail 8 I) and Blat ver 2.4 In-reply-to: (message from Brian Inglis on Mon, 11 Apr 2005 01:12:40 -0600) Subject: Re: DJGPP v2.04 Bugs - suggested patch References: <10504092012 DOT AA16787 AT clio DOT rice DOT edu> <200504101156 DOT j3ABu1k5002657 AT speedy DOT ludd DOT ltu DOT se> <01c53e00$Blat.v2.4$eacdb8c0 AT zahav DOT net DOT il> <01c53e48$Blat.v2.4$1e183ec0 AT zahav DOT net DOT il> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Mon, 11 Apr 2005 01:12:40 -0600 > From: Brian Inglis > > >Therefore, I think we have some kind of bug here, which should be > >investigated. The trick with a signal handler is just a means to ease > >that investigation. > > The OS vendor probably prefers the term feature. > I fail to see why an OS would allow a write, that it has already > rejected, to complete on fflush() or fclose(). This is a misunderstanding: I was talking about a DJGPP bug, not about the OS bug/feature. Our library functions should detect this condition (that a buffer doesn't get written, part of it or all of it), whether the OS helps us or not. If we somehow don't detect this, we should first fix this bug. After we do, we can discuss what to do when this condition happens.