cin >> string // multiple lines

Hi,

I have written a method that takes data for an std::string and processes it.
I now (taking a step back) want to get this line from user. the string may have multiple line.. (meaning that i can't read only until '\n', and I have as certain const char* which is the way to stop the input.
So, what would be a way to check when to stop adding the istream to std::string?

Thanks....

Sure, there are several ways to do that. One would be to read a line at a time and just accumulate a long string from each line of text.

Let's say we have a file that looks something like this:

Code:

---

Some text
More text
Another line of text
:end

---

You can then read a line at a time, and if it's not ":end", you continue with the next line.

If the :end can be anywhere in the text, it gets a bit more complicated.

For more help, it would be useful if you can describe the format in more detail.

--
Mats

ok. so here it is...
I'm not reading from a file, rather i'm reciving input from user.
I prefer to process the data only after i've collected all of it, so i can decide what allocations to make before I start working with, rather than allocation dynamicly after each entery.
The input is in the form of:

Code:

---

<Song> <We Dont Need No Education 1> <125>
<Song> <We Dont Need No Education 2> <78>
<Song> <We Dont Need No Education 3> <366>
<End song list>

---

The same principle applies to both direct user input and file input.
However, if the input is in a form where EACH line is a standalone complete packet of data - as you show it - then I would suggest a vector of std::string, and each line stored as a string. Seems much easier to deal with than to merge a bunch of strings together and then separating it out at the other end [sometimes that's what NEEDS to be done, but this doesn't seem like such a case].

--
Mats

being part of a school assignment, we are explicity forbidden to use STL...
therefore, this is one of those cases....

Ok, so make it an array of 100 arrays of char - if you get more than 100 lines of input from the user without <End song list>, process those 100 lines and then go back ask for more.

Making a very long string will just make it complicated.

--
Mats

if you say so...
thanks

Of course, the other factor is "do you actually need to accumulate a set of strings, then process them" for a practical [or assignment] reason?

--
Mats