Aww, sure, is this still the issue passing 3 months?here:
http://www.phwinfo.com/forum/comp-lang-cplus/463378-input-cin.html
(note: news.virginmedia.com == paul as in OP)
<quote>
09/18/10, 10:55 #18
news.virginmedia.com
Re: input to cin
--------------------------------------------------------------------------------
Is this is forum about the C++ standards? No.
So now YOU want to change the context to that of the standards?
You are also missing the big picture, that is you fail to acknowledge the
stream object.
As the >> operator is a member of the stream object I think It is
unreasonable to ignore it.
You , like Francesco, seem to be focusing ONLY on the extraction. You seem
to be trying to say that the main input process is extraction from the
stream to an object.
Ok lets say we are creating an input processing function, what is one of
the
first things this function must to do?
Check for successful input.
Yes this function can be called an input function , or an input processing
function, but context of input here is input to the function because the
focus is the function.
If the focus is the stream the input is input to stream.
When people write standards their context is different as they are
defining
a language, let me explain:
Suppose we a given a project to create a C++ stream library that reads and
write to a USB device.
But the C++ standards don't define USB devices, therefore its not a valid
C++ program? Of course this is wrong, it's is because the C++ standards
are
in a different context.
You seem to be misinterpreting the purpose of the C++ standards as a
definition of the contextual interpretation of software engineering terms.
The C++ Standards is simply a guide that defines the expected behavior of
the language, it certainly doesn't define software engineering terms.
</quote>