Projects > Discussion

The Alternate Extension - Error-Safe or File Size?

<< < (2/2)

Ben:
I wouldn't say that you need to else EVERYTHING. But there are times when you can get random pointer errors that are just annoying and you can't see why.
Hell I suppose it could have stopped a few pointer errors, but if you compile every three seconds then you should be able to realise where the actual error is - in the last line you wrote :-p.

They aren't necessary in a final version, unless they keep getting called for some reason. But if your code is solid enough you won't need it and the only pointer errors you'll get will be windows fault.

aab:
Try, catch yeah, But youll still need if, else somewhere the exception handler to throw your own exceptions (excluding the built-ins or libraries exps, which in the end will compile under a condition once again)
Then in the catch block messages can be collectively reported.

Navigation

[0] Message Index

[*] Previous page