From: James Youngman <JYoungman AT vggas DOT com>
Newsgroups: gnu.gcc.help,comp.os.os2.programmer.misc,comp.os.msdos.djgpp
Subject: Re: C++ constructor problem solved!! Read how, it might come in useful in your future programs!
Date: 20 Jan 1998 15:52:18 +0000
Organization: VG Gas Analysis Systems
Lines: 11
Sender: james AT XENON
Message-ID: <wkzpkrnnwt.fsf@vggas.com>
References: <bWLoegW7sFse-pn2-bxyqvlUyVUyY AT localhost>
	<34C2817A DOT 5547BE86 AT alcyone DOT com>
	<JgXSRD37O5mZ-pn2-GDBMovdtZi5F AT beaver_pc DOT reksoft DOT ru>
	<j5l3eik48xw DOT fsf AT tcadcs6 DOT sc DOT intel DOT com>
NNTP-Posting-Host: uriel.vggas.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

>>>>> "Claus" == Claus Fischer <cfischer AT tcadcs6 DOT sc DOT intel DOT com> writes:

  Claus> In reply to the previous thread, I posted that explicitely
  Claus> calling constructors is (to my knowledge) NOT possible. I
  Claus> might be wrong, but I think the standard requires a temporary
  Claus> object to be created. At least ARM says so. If you have
  Claus> better knowledge, please mail me.

IIRC explicitly calling the constructor on a region of memory is OK in
the circumstances where the constructor hasn't elready been called
(i.e. you haven't used new or an auto or static instance).