How about checking for NULL?

Look this code:
... CCSprite *pobSprite = new CCSprite(); if (pobSprite && pobSprite->initWithFile(pszFileName)) ...
After new operator never returns NULL, and is likely to be an exception bad_alloc, why check for Null?

http://stackoverflow.com/questions/550451/will-new-return-null-in-any-case

So we had to catch the exception and not check for NULL.