hrmm i was wondering if someone could jsut write a very simple loop, that reads a line at a time from a file.
something like
Code:istream& Message::read(istream& stream){ while( end of file ) { getline(....?...); /* read an int on next line of file? */ getline(....?...); } return stream; }
ok this is what is happennig
i have..
and the function read is ..Code:while(msg.read(inFile)!=0) msg.print(cout) << endl;
and in my file i'll haveCode:istream& Message::read(istream& stream){ getline(stream, animalName); getline(stream, animalType); stream >> age; return stream; }
Jack
Dog
3
Missy
Cat
6
but my output only outputs
Jack is a Dog and he is 3 years old.
How come it did not read the Cat?
> stream >> age;
This will leave a newline on the stream
Which will really upset your attempt at getline() in the next call to read
It's best to stick to getline to read all lines, then use something else to extract bits of information from a line, if that is what you want to do
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
thanks
hrm now that i've change all into getline statements..
it reads the stuff from the file, but the printout is a bit weird..
in my file i'll have
Jack
Dog
3
Missy
Cat
6
but my output only outputs
Jack is a Dog and is 3 years old.
Missy is a Cat and is 6 years old.
Cat and is 6 years old.
last line???
Post the latest code
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
i've been fiddling around with it, and i've got it working...
not too sure what was going on..
thanks anyway
>>not too sure what was going on..
Then how are you sure that it is fixed? Bugs do not disappear, and messing with your code randomly is not a good way to try removing them. When you have a bug, find out exactly where it is coming from and what is causing it before you change the code in any way. Now you have code that is suspect because the original bug may be hidden and you may have introduced more bugs by fiddling with the code.
The best way to regain confidence in your program is to perform regression testing on older versions. The goal is to verify that what worked correctly before continues to work correctly and what was broken before works correctly now.
paperbox005>>while( end of file )
Shouldn't this be while(eof())
Child who knows C++Using Borland C/C++ Compiler 5.5 (Command Line Version)
I don't know of any eof function so I'm assuming you meant feof. Given that:
http://faq.cprogramming.com/cgi-bin/...&id=1043284351
Thantos, here is a breif explanation of the eof function: http://mathbits.com/MathBits/CompSci/Files/End.htm
I'm surprised an experienced programmer, like you Thantos, didn't know this and a noob did.Originally Posted by the website I posted Above
Last edited by C++Child; 07-31-2004 at 07:27 PM.
Child who knows C++Using Borland C/C++ Compiler 5.5 (Command Line Version)
Maybe because the function is a member function and not a function by itself like you had it.
Last edited by Thantos; 07-31-2004 at 09:07 PM.
You said that wasn't a function at all! You said >>Did you mean feof()?
Child who knows C++Using Borland C/C++ Compiler 5.5 (Command Line Version)
Is it me or is c++ child one of the most rudest person's. He comes in with such an attitude. Don't insult thantos he could own you anyday of the week and don't even think about questioning his knowlege.
Last edited by prog-bman; 08-01-2004 at 09:21 AM.
Woop?
I actually think he's a reincarnation of C+++C_forever.
