Where's the constructor?

[Richard Hadsell]

Joe Buck wrote:
> 
> Correct.  In this particular case (no return statement at all), an
> error might be appropriate.

Then promote this warning into an error.  I expect a warning to mean
that some kind of default or best-guess behavior was generated, when the
programmer might have intended something else.  In this case, the
compiler does nothing at all.  If it is too complicated an issue to
construct a valid object, it's better to say the program is in error. 
Does the standard allow you to call this an error?  Or does it require
the compiler to generate code, no matter what?

-- 
Dick Hadsell			914-381-8400  Fax: 914-381-9790
Reply-to:			hadsell@blueskystudios.com
Blue Sky | VIFX			http://www.blueskystudios.com
1 South Road, Harrison, NY 10528