You're right. I'd already considered this, and so decided that the "nulling" ctor overload would take an address of the handle. This has the big advantage that there can be no such confusion, and the small disadvantage that you can't "inline" the allocation function invocation with the scoped_handle ctor. ;-)

Actually, I'm not sure I understand what you mean.
The problem I mentioned was specifically related to and assumed taking a reference.
Do you mean something like taking a reference as opposed to taking a const reference to not compile (or select another ctor) when a temp is given?

This should all work ticketyboo (LOL, don't you love the silly English and our daft expressions!). Just give me a few days to get over the last book push.

BigBoy

You're in a good mood :-).
Adi