2009-09-14

Being a NULL pointer!

So..

I am a Software Test engg. with 4 years of irrelevant industry experience. In all the highest highs( MVC fmwks,linux and Oracle 11g) and lowest lows(iseries, AIX 5.3,DB2) , of technology, the one bit that has really fascinated me are the exceptions!

As a tester I could always raise a sev1 P1 bug the moment I saw one! And there were always so many, a java heap here, an array out of bonds a null pointer an IOexecption..Gee! And as a quest of pure academic interest I was intrigued by who invented them, classified them and where could i find more!
The exceptions define me so well. Ironically I am fine tuned in the art of finding them and yet
I am exceptionally flawed!

Exceptions defy rules.And they are definitely beyond any level of structured error handling! ( sounds familiar!)
A null pointer indicates that it points to no object.. so reminiscent of me!.My friend taught me that a Null Pointer should not be caught, they should be resolved. As they mean "flaws in your program". For example you can always declare/catch a "throws IOException".. But a null pointer tch tch.. int k = 0 ;100/k ; Improperly written "code" would always throw a null pointer.

To be contd: I have an entire list to go before I throw an arrayoutofbounds!!

No comments: