I'd be interested to see how ON ERROR could catch a subroutine call
failure. And I'd ball-up and toss my stuff in a heartbeat. No pride
here... -BD
On 1/30/2014 2:52 PM, Anthonys Lists wrote:
On 30/01/2014 18:35, Bruce Decker wrote:
Good points. My view is that it is usually not a matter of whether
the failure should be catastrophic. It's usually a matter of who
should be in in control of the catastrophe. If you call a object
that bombs, the caller will never know why because control never
returns to the caller.
Which is the whole point of the object-oriented programming feature
try/catch, or even the ON ERROR statement that has been added to
databasic in "recent" years.
Cheers,
Wol
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
