Re: [boost] [scope_guard] New revision available + naming consideration

David Abrahams wrote:

Maybe because it allows more than a literal zero?

But then again, so does assignment (and implicit conversion) to any pointer? I'd like to have code like the following: boost::shared_ptr<int> foo() { return 0; /* instead of boost::shared_ptr<int>() */ } boost::shared_ptr<int> p(new int(42)); p = 0; // instead of p.reset()