From:	sparhawk AT eunet DOT at (Gerhard Gruber)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Deconstructors
Date:	Sat, 18 Jul 1998 21:37:57 GMT
Organization:	Customer of EUnet Austria
Lines:	38
Message-ID:	<35b31422.618669@news.Austria.EU.net>
References:	<35AFE02F DOT 3C4857ED AT logic-gate DOT com> <35AFEF99 DOT 29955266 AT alcyone DOT com> <35b6691c DOT 3375145 AT news DOT Austria DOT EU DOT net> <35B06FF0 DOT E4E83F1 AT alcyone DOT com> <35b0757c DOT 6543544 AT news DOT Austria DOT EU DOT net> <35B0784A DOT 666728D4 AT alcyone DOT com>
NNTP-Posting-Host:	e006.dynamic.vienna.at.eu.net
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Destination: Erik Max Francis <max AT alcyone DOT com>
From: Gruber Gerhard
Group: comp.os.msdos.djgpp
Date: Sat, 18 Jul 1998 03:26:18 -0700:

>> I just used main. You can use any other function as main is not really
>> special
>> as a function.
>
>Your example involved a block off of main, which is what I was talking
>about.

Well. And if next time I write foo() instead of main, then you argue that foo
is not a proper function or that this doesn't apply to foo as well?

>If c isn't being created and destructed every iteration of the loop,
>you've got a problem.

That's right.

>Again:  construction/destruction and reservation of memory on the stack
>aren't necessarily one and the same, although I'm not even sure that
>your statement about that standard behavior is true.  (It certainly
>isn't required by the C/C++ function model.)

I never said that this is required by the stanrd, but usually compiler do it
this way.

--
Bye,
   Gerhard

email: sparhawk AT eunet DOT at
       g DOT gruber AT sis DOT co DOT at

Spelling corrections are appreciated.

- Raw text -