Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: "Dylan Cuthbert" Newsgroups: gmane.os.cygwin Subject: CR not stripped when using stream::getline with latest cygwin/gcc 3.1.1 combo? Date: Thu, 18 Jul 2002 22:21:44 +0900 Lines: 25 Message-ID: NNTP-Posting-Host: pppa20.kyoto-ip.dti.ne.jp Mime-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1026998390 32200 210.159.246.20 (18 Jul 2002 13:19:50 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Thu, 18 Jul 2002 13:19:50 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Hello all, There's something up with the latest cygwin (1.3.2-2) and/or gcc 3.1.1. Code that worked fine with text files in cygwin 1.3.10 and gcc 3.1.0 is now broken. The problem is that the carriage return is being left in the text data returned by ifstream::getline(). It doesn't matter if the file being read is on a network mount or simply in a local directory. It used to strip both. The file, is of course opened in default mode, ie. text. Is this intentional, ie. a "feature" of the newer stdlib/gcc and therefore an oversight in our code? Or is it a problem somewhere in the configuration of the latest version of gcc/stdlib for cygwin? I think this problem is linked to the spurious cvs error I reported last week that occurs every time I use cvs now. (started occurring after updating cygwin et al) Regards -- --------------------------------- Q-Games, Dylan Cuthbert. http://www.q-games.com -- 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/