Date: Thu, 13 Nov 1997 12:16:06 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: sl <SL AT usemail DOT com>
cc: DJGPP mailing list <djgpp AT delorie DOT com>
Subject: Re: problem with fstream it erases my input file !
In-Reply-To: <199711121927.OAA22133@delorie.com>
Message-ID: <Pine.SUN.3.91.971113121543.23305L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 12 Nov 1997, sl wrote:

> >AFAIK this is a bug in libiostream. The workaround is to use
> >open() to open the file in the desired mode and
> >then feed the handle into the constructor. 
> 
> This bug is present even in the latest version of DJGPP? Is it going
> to be fixed in the next release?

libiostream (and the rest of C++ classes) are not part of DJGPP, it's
just a port of GNU C++ library.  As such, its update schedule is
separate from the DJGPP releases, like all the rest of the ports.

Therefore, this bug, if it's indeed a bug, will be fixed only when the
next port of libg++ is released.  And if people who care about the
quality of C++ classes don't sit down, track down that bug and submit
patches to DJ Delorie, or better yet, port the latest GNU version of
libg++, the answer is probably ``never''.  Using workarounds is not
good enough (IMHO).

> When is the next release? :)

You should never ask this.  The only honest reply is ``nobody knows''.