«

{ Note: cross-posed to comp.lang.java.programmer. -mod/vdv }

Typically, languages do not allow an object to be constructed more
then once. Would allowing (re) construction cause a security failure,
perhaps indirectly, because of assumptions made by existing code bases?

[For instance, it is possible that an object may have file buffers open
and multiple constructor invocations may cause undesired behavior.]


[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]

> Typically, languages do not allow an object to be constructed more
> then once. Would allowing (re) construction cause a security failure,
> perhaps indirectly, because of assumptions made by existing code bases?

I have never heard of reconstruction and -- as I understand it -- it appears to
be bad style to me, and you have already given reasons. Why would you want to do
this?

For Java collections, you can clear() them, and for other objects (mainly
representing algorithms) like parsers you may init() or reset() them.
Still, it is a question of style whether or not you want objects to be
init()ialised more than once.

Cheers,
Simon

f'up2 cljp