[Openroad-users] OpenROAD runtime error handling

[Michael Leo]

Jim,

Java borrowed the "try-catch" and exception scoping/bubbling mechanism
from Ada.  It works very well, but like any sword, it has two sharp edges.

Java developers constantly "bury" exception information because they either
don't understand exceptions, have never supported a production system, or
don't have an exception handling architecture laid out.

It would be nice in OpenROAD.  The OR develop crowd seems to understand
production engineering needs.  It would be a great tool in the toolbox.

Mike Leo

Antill, Jim wrote:
> Robert,
>
> A rather round-about way of doing it would be as follows:
>
> One thing I did a while back was to write a C# routine to monitor a file,
> effectively doing the equivalent of a UNIX tail -f on the file. This worked,
> if I remember correctly, by an event being triggered when the file was
> changed. In fact I used it to redirect the w4gl.log file to a window that
> stayed on top. (If you want the code I've probably got it lying around
> somewhere.)
>
> This could be changed so that when a change to the file is detected the new
> segment is checked for E_ chars. If any are found an external event could be
> sent back to the OpenROAD application to say that an error was received.
>
> I must admit to liking Java's try-catch error handling, something that would
> suit some parts of OpenROAD e.g DynamicExpressionNotValidException rather
> than checking for NULL dynexpr.
>
> Hope that's of some interest.
>
> Regards,
> Jim
>
> -----Original Message-----
> From: openroad-users-bounces at peerlessit.com
> [mailto:openroad-users-bounces at peerlessit.com]On Behalf Of Robert Allely
> Sent: 18 June 2007 23:07
> To: International OpenROAD Users
> Subject: [Openroad-users] OpenROAD runtime error handling
>
>
> *************************************
>
> This e-mail has been received by the Revenue Internet e-mail service. (IP)
>
> *************************************
>
> Is there a good way to trap run time errors - which seem to only appear
> in the w4gl log and trace window - so the user can see that something
> has gone wrong without having to look at the trace window? I was
> thinking of a setting like DBMSErrorPrinting .
>
> Robert Allely
> Ports of Auckland Ltd
> NZ
> ***
> This e-mail is privileged and confidential.  If you are not the intended
> recipient please delete the message and notify the sender at Ports of
> Auckland Limited.
> ***
>
> ________________________________________________________________
> OpenROAD-Users mailing list
>
> You can maintain your subscription here:
> http://www.peerlessit.com/mailman/listinfo/openroad-users
>
> To unsubscribe click on this link
> mailto:openroad-users-unsubscribe at peerlessit.com&subject=unsubscribe
>
> To subscribe click on this link
> mailto:openroad-users-subscribe at peerlessit.com&subject=subscribe 
>
>
> ************************
>
> This message has been delivered to the Internet by the Revenue Internet e-mail service (OP)
>
> *************************
>
> ________________________________________________________________
> OpenROAD-Users mailing list
>
> You can maintain your subscription here:
> http://www.peerlessit.com/mailman/listinfo/openroad-users
>
> To unsubscribe click on this link
> mailto:openroad-users-unsubscribe at peerlessit.com&subject=unsubscribe
>
> To subscribe click on this link
> mailto:openroad-users-subscribe at peerlessit.com&subject=subscribe 
>
>
>