Typically, it should never return null. The only case (thinking off the top of my head) is if somehow the program ran out of memory just at the point of creating the task -- which would be highly unlikely. If there's even a small chance that something could fail, then Chilkat must be able to return either null or false. Not checking for null leaves open the very very tiny possibility that your program could crash rather than fail gracefully.
answered Jan 09 '16 at 19:09
Thanks for your answer. When my program runs out of momery I will get an OutOfMemoryException anyway.
answered Jan 10 '16 at 01:36