[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re Debug messages
- Subject: Re: Re Debug messages
- From: Stuart Booth
- Date: Wed, 10 Mar 2004 21:43:00 +0000
On Wed, 10 Mar 2004 21:21:25 -0000, "Patrick Lidstone \(Personal
E-mail\)" <<a
href="/group/xAP_developer/post?postID=du3QQYOVvDEakhpcKn54MsL-wCR5PkhDlrNLe6Bh_xLKrInYd_xaR_YL7yJJ7iEaL4XtsLZhV6CVxWA">patrick@l...</a>>
wrote:
>1) Include an error number. Ideally we need to ensure these are unique
>(perhaps by combining with the vendor ID).
I did wonder about that but discarded it as I felt it could be
included in the detail line. However I imagine it would be useful to
allow for either or even both so there is a human and machine readable
flavour available.
>2) Distinguish between technical errors (bugs) and application errors
>(stuff that didn't work out right, or couldn't be complete).
I like that plan. How about:
Class=xAP.Error
Error
{ ... }
Error.Application
{ ... }
(or Error.Device since we talk in terms of DeviceIDs)
S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=v7k7kvC4yJbjdeqqjO388JmJ3BJpPCfFFM7oiSp8d6czEAvJFNc1cglQ2RFM3RYaaJhfgeT3FZYqL2BY8jPmHUti">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net
<a href="http://www.xapautomation.org/">http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/">http://www.xapframework.net/</a>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|