public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: salvador <salvador@inti.gov.ar>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/4419: ifstream::get(buffer,len) stops reading when an  empty line appears.
Date: Mon, 10 Dec 2001 04:46:00 -0000	[thread overview]
Message-ID: <20011210124603.3611.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/4419; it has been noted by GNATS.

From: salvador <salvador@inti.gov.ar>
To: paolo@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
 	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,  pavenis@lanet.lv
Subject: Re: libstdc++/4419: ifstream::get(buffer,len) stops reading when an 
 empty line appears.
Date: Mon, 10 Dec 2001 09:44:05 -0300

 paolo@gcc.gnu.org wrote:
 
 > Synopsis: ifstream::get(buffer,len) stops reading when an empty line appears.
 >
 > Responsible-Changed-From-To: unassigned->paolo
 > Responsible-Changed-By: paolo
 > Responsible-Changed-When: Sat Dec  8 02:42:46 2001
 > Responsible-Changed-Why:
 >     Looking into it.
 > State-Changed-From-To: open->feedback
 > State-Changed-By: paolo
 > State-Changed-When: Sat Dec  8 02:42:46 2001
 > State-Changed-Why:
 >     Why don't you use something like:
 >
 >       while(!fileToView.eof())
 >         {
 >           fileToView.getline(line, sizeof line);
 >           printf("%d\n",strlen(line));
 >         }
 >
 >     ???
 
 That's more or less what I'm doing now. But the problem is that I was porting all
 code that used the other way and was working for years.
 As this code is an example of a library I'm affraid a lot of people will be using the
 old approach and failing.
 I got really confused when the code break without any apparent reason.
 
 SET
 
 BTW: What I use now is a macro, it expands to getline for gcc (libstdc++ v2 and v3)
 but I was forced to expand it to a function call for Borland compilers where the
 getline fails to extract the trailing newline.
 
 --
 Salvador Eduardo Tropea (SET). (Electronics Engineer)
 Visit my home page: http://welcome.to/SetSoft or
 http://www.geocities.com/SiliconValley/Vista/6552/
 Alternative e-mail: set@computer.org set@ieee.org
 Address: Curapaligue 2124, Caseros, 3 de Febrero
 Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013
 
 
 


             reply	other threads:[~2001-12-10 12:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10  4:46 salvador [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-11 13:35 pme
2001-12-08  2:46 paolo
2001-12-08  2:42 paolo
2001-09-28 15:06 salvador

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=20011210124603.3611.qmail@sources.redhat.com \
    --to=salvador@inti.gov.ar \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=paolo@gcc.gnu.org \
    /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).