public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@syncretize.net>
To: "'Dylan Cuthbert'" <dylan@q-games.com>, <cygwin@cygwin.com>
Subject: RE: CR not stripped when using stream::getline with latest cygwin/gcc 3.1.1 combo?
Date: Thu, 18 Jul 2002 08:05:00 -0000	[thread overview]
Message-ID: <000101c22e5e$4df04270$0200a8c0@lifelesswks> (raw)
In-Reply-To: <ah6f9l$ve8$1@main.gmane.org>



> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Dylan Cuthbert
> Sent: Thursday, 18 July 2002 11:22 PM
> To: cygwin@cygwin.com
> Subject: CR not stripped when using stream::getline with 
> latest cygwin/gcc 3.1.1 combo?
> 
> 
> 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.

Default mode is not text. It is determined by whether you link with a
foomode.o file, and your mount table.
 
Rob


--
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/

  reply	other threads:[~2002-07-18 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  7:48 Dylan Cuthbert
2002-07-18  8:05 ` Robert Collins [this message]
2002-07-18  9:10   ` Dylan Cuthbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000101c22e5e$4df04270$0200a8c0@lifelesswks' \
    --to=robert.collins@syncretize.net \
    --cc=cygwin@cygwin.com \
    --cc=dylan@q-games.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).