Christopher Smith wrote:
That's the kind of thing I was thinking about. All of a sudden, it's
not RIAA any more, since all the references to what appears to be a
stack variable are actually copies of those variables.
I don't know if I would call say it not being RIAA any more,
Well, I meant that it doesn't look like RIAA, just like
{ Alpha aaa(...);
aaa.something();
{
aaa.somethingelse();
}
}
doesn't look like the inner block allocates something.
Maybe that's just because I don't know all the baroque in C++, tho.
which is bad, bad, bad, but normally you'd be using a boost::scoped_ptr
I.e., there are so *many* ways to screw up, you have to pick exactly the
right one to get the compiler to tell you.
Personally, it boggles my mind when I see G++ issue warnings for things
that can't possibly work right. Shouldn't "your program will act in
undefined ways if you invoke this function" be an error?
--
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."
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
