Re: [boost] Why no non-null smart pointers?

static ChessPieceNull chessPieceNull; static shared_ptr < ChessPiece > nullsp( &chessPieceNull, nullDeleter () ); return nullsp;

Thanks for your suggestion. Agree this is usually preferable, but since the code is in the specialization (within a user snap-in) then of course the user can decide which approach he prefers. -- View this message in context: http://boost.2283326.n4.nabble.com/Why-no-non-null-smart-pointers-tp2642959p... Sent from the Boost - Dev mailing list archive at Nabble.com.