"E. Gladyshev" <[EMAIL PROTECTED]> writes: >> The class getting constructed/destroyed has full control over that or >> the language is utterly bustificated. > > I think construct/destroy can be implemented as non-customizable > static functions in boost just for convinence.
Just how do you propose to prevent people from writing their own construct/destroy functions? And if they write an allocator from scratch, but *don't* provide construct/destroy manually, where will they come from? -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
