|
![](/i/fill.gif) |
Fredrik Eriksson wrote:
> The words allocated with 'ios::xalloc' are not related to any
> user-defined types. They have only whatever meaning you choose to give
> them.
Right, OK.
>> and if you cast it to a pointer, it still doesn't get cleaned up when
>> the stream goes out of scope,
>
> Correct. The stream object itself neither knows nor cares what you store
> there.
Yeah. I'd just been thinking about Warp's example earlier that needed
"weak" references to actually not "leak" resources. I was trying to
figure out how C++ handled it, if at all.
> If you mean "automatically" then not at all.
OK.
> Depending on your definition of "very limited", yes.
By "limited" I mean "for anything other than an integer, like say an
instance of a user-defined class." :-)
Thanks for the clarification!
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Post a reply to this message
|
![](/i/fill.gif) |