* David Nugent >>> Shane Day  

 >> It is a bit of a bugger.  I've had the same problem when
 >> using cin.  After using a cin.get(char*,int,int) I've found
 >> it is necessary to do a cin.get() after _every_ cin call.

 DN> Then use istream::getline(), where the '\n' is automatically
 DN> discarded, or better yet, define a string class which allows you
 DN> to accept and parse the precise object you're looking for.
 DN> There's little point in using an OOP language unless you're going
 DN> to follow the same philosophy.

I do, normally.  The situation above happened when a teacher wanted me to
write a quick program to do a brain-dead task.

Doesn't istream::getline() include the '\n' in the target string?

Shane

--- FMail 0.94