Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (Jim Adcock)
Newsgroups: comp.lang.c++
Subject: Re: Call of constructors by vectors
Message-ID: <6590151@hplsla.HP.COM>
Date: 14 Jun 89 23:14:09 GMT
References: <1904@mas1.UUCP>
Organization: HP Lake Stevens, WA
Lines: 9

> >inline SomeClass::SomeClass(){}
> >
> Because the SomeClass initializer may do a "new" and you want 100 objects 
> allocated.  See Stroustrup section 5.5.5 page 162.  What do I win? :-)

How can the SomeClass initializer do a "new" when I pointed out its not
doing anything?  I was arguing that I would at least expect a compiler
to recognize when a class has a no-op initializer and not bother calling
it 100 times ???