From: Christopher Croughton <crough45 AT amc DOT de>
Message-Id: <97Nov5.122114gmt+0100.11651@internet01.amc.de>
Subject: Re: Writing to a file from dtor doesn't work!
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Wed, 5 Nov 1997 11:24:13 +0100
Cc: crough45 AT amc DOT de, eyal DOT ben-david AT aks DOT com, djgpp AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.971105121058.460J-100000@is> from "Eli Zaretskii" at Nov 5, 97 11:12:25 am
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

Eli Zaretskii wrote:
> 
> On Tue, 4 Nov 1997, Chris Croughton wrote:
> 
> > It seems to be therefore a DJGPP bug (in the library?  I'm
> > not sure which bit of it the startup/exit code is in).
> 
> This *should* be DJGPP-specific: exactly how the open handles are closed 
> when the program shuts down is defined by the library internals.  And 
> DJGPP's library was written specifically for DJGPP.

Indeed, but the contrast was with it being a bug in the specification of
C++, if C++ required that the dtors were called after the files were closed.
If everyone did it the same way then it would be a specification bag and so
we'd have to put up with it, rather than being a DJGPP bug.

(My question about whether it was in the library was due to experience
with other compilers where the startup/exit code is in a separate module
linked explicitly by the compiler rather than in the library itself.  I'm
glad to hear that it's in a standard library module...)

Chris C