In-memory array output stream?

[Laurens]

Hi,
My application needs to create in-memory arrays, the size of which is not
known, or very hard to calculate, in advance. I would like to stream the
data using the standard I/O class framework. The class should take care of
the underlying memory management. Now which class is most suitable for this?
(Assuming there is one.) Will std::ostrstream do the trick?

In Java I use java.io.ByteArr ayOutputStream to create in-memory data.
Thanks
-Laurens

[Jeff Schwab]

Laurens wrote:

Hi,
My application needs to create in-memory arrays, the size of which is not
known, or very hard to calculate, in advance
On second reading, I assume you mean "in advance of the I/O I'm about to
tell you about."
I would like to stream the
data using the standard I/O class framework. The class should take care of
the underlying memory management. Now which class is most suitable for this?
(Assuming there is one.) Will std::ostrstream do the trick?
Yes.
In Java I use java.io.ByteArr ayOutputStream to create in-memory data.
When you spit the string from the ostrstream into the output stream,
make sure you flush the buffer. Most of the standard c++ streams (cout,
clog, fstream's, etc.) are buffered by default.


Thanks
-Laurens

[Dietmar Kuehl]

"Laurens" <sp**@block.com > wrote:

My application needs to create in-memory arrays, the size of which is not
known, or very hard to calculate, in advance. I would like to stream the
data using the standard I/O class framework. The class should take care of
the underlying memory management. Now which class is most suitable for this?
(Assuming there is one.) Will std::ostrstream do the trick?

Yes, it would. However, you should probably rather use 'std::ostringst ream'
because 'std::ostrstrea m' is deprected: it has several serious problems
which 'std::ostringst ream' has not. The only issue which 'std::ostrstrea m'
solves which 'std::ostringst ream' does not is writing to a buffer supplied
by the user. However, a corresponding stream buffer is easy to write and
not what you need if you can't predict the size of the generated output.
--
<mailto:di***** ******@yahoo.co m> <http://www.dietmar-kuehl.de/>
Phaidros eaSE - Easy Software Engineering: <http://www.phaidros.co m/>