Hi Itamar, it's true - boost:shared_ptr might be overkill in many cases. But usage of raw pointers is dangerous and evil. Please use boost::scoped_ptr instead (or std::auto_ptr if copies are needed). But never ever use raw pointers. Especially since I've seen that many of the topics discussed here are around memory leaks I have to make a strong point for the use of smartpointers. Btw: boost::scoped_ptr should result in absolutely no performance penalty - you just get more safety and also exception handling for free...
Where would be a good point to start with help (e.g. which parts should be ported to smartpointers first)? Would you like to always use boost::shared_ptr in API-functions or should one think of std::auto_ptr instead (thus explicitly taking ownership)? Btw: Why are there macros for new and delete in CLucene? Henning ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ CLucene-developers mailing list CLucene-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/clucene-developers
