Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.1.1.5.2.20021218213609.00bdc968@www.marble.be>
X-Sender:	gerrit AT www DOT marble DOT be
Date:	Wed, 18 Dec 2002 21:40:20 +0100
To:	cygwin AT cygwin DOT com
From:	Gerrit Cap <Gerrit DOT Cap AT marble DOT be>
Subject:	c++ ifstream problem with gcc 3.2
Mime-Version:	1.0

Hello,

I recently encountered the problem with the gcc 3.2 compiler of cygwin 
using ifstream. Basically it is the same problem as mentioned in 
http://gcc.gnu.org/ml/gcc-help/2002-06/msg00079.html although this is about 
gnu cc 3.0. I thought that this was already fixed. The problem is that when 
a ifstream object is closed and than reopened with the open method to open 
another file, no data is returned. But if one uses 2 ifstream objects, 
everything works perfectly. Is this a known issue with c++ on cygwin ?

Gerrit.


-------------------- Marble Consulting ----------------------
Gerrit Cap                      http://www.marble.be/
OO Solutions Engineer           mailto:Gerrit DOT Cap AT marble DOT be
Marble Consulting
Blauwe Gaanweg, 53              tel : +32 475  72.94.36
B-9150 Kruibeke-Bazel           fax : +32 3   744.19.17
Belgium
-------------------- Marble Consulting ----------------------
There is only one thing in the world worse than being witty,
and thats not being witty.          (Monthy Python)



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -