David Graham wrote:
I had been developing an RB 6 application using the TCPsocket for a while
under Windows, with no problems, but when I just tested it under OS10.4, it
threw an unhandled Nilobject exception, and would not compile. The message
asked that I contact the RB folks with any details, but I have better things
to do than see if I can figure out any more details, or go through RB's
hoops for submitting feedback. I did try, but when I tried to submit it, I
was greeted with a "The page cannot be displayed" screen in my browser.
I'll just go back to my PC.
Hopefully someone at RB will see this and realize that it would be really
helpful if this unhandled Nilobject exception message could be fleshed out
with some indication of what part of the code is causing the problem.
David:
This is a problem in almost any complex app. The solution I adopted a
long time ago was to have a central handler for errors which is fed
with a short string indicating the routine which is the source of the
problem when it is envoked.
My RB app is liberally sprinkled with short exception blocks like:
Exception Error
LocStr = " App 4"
HandleError(error)
Where HandleError is my central handler and LocStr is a global variable.
The unhandled exception evokes the same error handler with a "G2" location.
If I get G2 messages it indicates a need for more exception blocks like
the first one.
Regards,
Jim Payne
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
