From: Alp Mestan (alp_at_[hidden])
Date: 2008-08-02 18:50:23
Now everything is okay. The compiler doesn't dislike your code anymore and I
don't get any execution problem.
However I don't see anything that would keep the nested pointer to be null.
Moreover, don't you want unnullable_ptr users to have a ready-to-use copy
constructor and = operator ?
I'm actually wondering if using a smart pointer and adding a non-null
condition checking wouldn't be prettier and faster than rewriting all from
As you'vre written this class, you probably had the need of writing such a
class. Can you give an exemple of situation where your class would solve a
problem or help a lot ?
-- Alp Mestan --- http://blog.mestan.fr/ --- http://alp.developpez.com/ --- In charge of the Qt, Algorithms and Artificial Intelligence sections on Developpez
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk