Boost C++ Libraries: Ticket #3401: has_new_operator fail if several new operators is overrided

Robert Ramey — Sun, 11 Oct 2009 21:20:56 GMT

Hmmm - I notice your name is the first on the list of authors in the source code for has_new_operator.hpp.

I suspect that I and john maddock made just minor tweaks. How about updating has_new_operator.hpp and sending it to me so I can check it in. This is much easier for me than diving back into this.

Now that I look at it, there is a "rutger" on the user list for this site. Could I just assign this to you and let you take care of this? Same would go for #3400. This would be very helpful to me.

Robert Ramey

anonymous — Mon, 12 Oct 2009 10:42:29 GMT

I've been meaning to look at this as well, but haven't had the time yet :-(

Before we get too carried away with any changes:

I'd prefer it if has_new_operator retained the existing semantics - which is to say returns true if the class has any of the new operator signatures overloaded.
With regard to splitting in 3: just remember that there are actually 6 (I think!) variations if we include the nothrow versions as well. Wait, make that 8 if we include the 2 placement versions! Not sure whether has_operator_new should return true for placement operator overload though?

Just thinking out loud yours, John.

anonymous — Mon, 12 Oct 2009 10:59:45 GMT

Will be fixed in Trunk shortly (but not the splitting up).

status changed; resolution set

John Maddock — Mon, 12 Oct 2009 11:00:04 GMT

status new → closed
resolution → fixed

(In [56730]) Fixes #3401.