Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!taumet!steve
From: steve@taumet.com (Stephen Clamage)
Newsgroups: comp.lang.c++
Subject: Re: New/Delete vs. Constructors/Destructors
Message-ID: <723@taumet.com>
Date: 11 May 91 19:26:35 GMT
References: <22592@shlump.lkg.dec.com>
Organization: Taumetric Corporation, San Diego
Lines: 14

s_johnson@csc32.enet.dec.com (Scott Johnson) writes:

>When creating and destroying objects, is it better to use the new/delete
>operators or is it better to explicitly call the constructors/destructors
>themselves?  Why is one method better than the other?

If I understand what you are asking, it is the same question as "Is it
better to have static/auto objects, or to allocate them on the heap?"
When you use new/delete, the constructor/destructor is called as part of
the operation.  The only questions are whether you want objects with the
lifetime of their scope, or whether you need dynamically created objects.
-- 

Steve Clamage, TauMetric Corp, steve@taumet.com