On 5/6/16, Rainer Weikusat <rainerweikusat@???> wrote:

(...)
> I'm dealing with a program where every allocation failure is
> meticolously passed up the call stack so that the top-most function can
> then cause the process to terminate and I've just recently decided that
> this is completley useless and that I want to get a message what failed,
> followed by program termination close to the point of failure
> instead. Using a null pointer deref to this effect is an IMHO clever
> idea I didn't think of so far.

Good for you.
Who will clean up resources if you are using some (temporary files,
shared memory, etc).
System administrator?

I know, memory is cheap, java programmer time is expensive nowadays.

:D

>
> NB: I'm not yet convinced that I'll end up using it but it's surely
> something to consider.

Hope not using your applications , no offence, just wasted over a year
of my life supporting similar beast -

try {
     parseAndSaveImportantDataToFile()
} catch ( Exception dummy) {
   /* java programmer time is expensive */
}

--
regards
piotr