Jerry Jankura wrote in a message to Mike Walker:
MW>The notation looks a little strange at first. Expecially for
MW>someone not used
MW>to C++ yet. :-) Can you tell me what you mean by "in-core" storage?
MW>Are you
MW>refering to writting to memory?
 JJ> You're correct on both counts - in-core storage is writing to a
 JJ> memory buffer (but doesn't using the term "in-core storage" sound
 JJ> better?) and the idea of using the left and right shift operators
 JJ> to insert and extract characters from a stream first looks strange.
Not only do the > operators look a little strange they tend to make things 
a little harder to read, at least for me. :-) This is especially the cause 
with complex formating requirements. 
Using the term in-core probably makes some sense. It fits in rather well with 
terminology used in other areas such as when an OS does a "core dump" do to a 
fault.
 JJ> Yep, if you write an insertion operator for an object, you can
 JJ> insert it into a stream just like you do a character or integer.
 JJ> But, the trick to remember is that you MUST write the operator.
Well I think I will be holding off on this for a while. Its probably a good 
idea to get the hang of the language first don't you think?
MW>Really I did not realize the stdio was parsed at run time. This would be a
MW>definate plus for stream io wouldn't it?
 JJ> I think so. Also, one fellow also mentioned that you can't run into
 JJ> problems caused by pushing the wrong kind of data onto the stack
 JJ> for the format expression.
So we have another plus for stream io then. 
   Mike....
--- timEd 1.10+
---------------