> > Is this actually a bug? I don't think you are supposed to call a
> > destructor directly in this situation. I would assume that the crash
> > comes when the destructor is called a second time when the program
> > exits main.
>
> It is legal to explicitly call a destructor but rarely needed.
Guy Maor wrote:
>
> It is legal to explicitly call a destructor but rarely needed. It
> certainly makes no sense in this case, as the destructor will be called
> twice.
>
> The question, it seems, is what was the programmer trying to do?
Well I haven't got a clue on that one as I didn't write t
On 4 Aug 1996, Rob Browning wrote:
> Is this actually a bug? I don't think you are supposed to call a
> destructor directly in this situation. I would assume that the crash
> comes when the destructor is called a second time when the program
> exits main.
It is legal to explicitly call a destru
Package: gcc
Version: 2.7.2-8
A recent posting on comp.os.linux.apps by
[EMAIL PROTECTED] (Dirk Alboth) can
be reproduced on my Debian system. In fact,
it seems to occur on a Sun with g++ too.
Here's a modified version of the program:
--
#include
void main( int argc, char **argv) {
ofstream
4 matches
Mail list logo
