Just a query from a user. If a localized error message exists, it will very probably be keyed to an OS error code. *IF* an OS error code were available at the point of failure, would it be possible and/or advisable to include it as part of the exception payload for transport to the handler? There need be no necessary relationship between the exception type and/or any "portable" error code.
BTW: I'd like to express one more strong preference for multiple exception
types.
"William E. Kempf"
<[EMAIL PROTECTED]> To: Boost mailing list
<[EMAIL PROTECTED]>
Sent by: cc:
boost-bounces@list Subject: Re: Re: [boost] Re: Next
revision of boost::thread & OS error code.
s.boost.org
01/10/2003 09:41
AM
Please respond to
Boost mailing list
<snip>
> Sorry, I meant what information do you have _portably_?
Depends on what you mean by "portable", I guess. In some cases I'll have
an error code... but like I illustrated before, I'm not convinced this is
"portable". Other times there's nothing available but the reason for an
error. But in the end, the question you just asked is exactly what I'm
asking ;).
William E. Kempf
[EMAIL PROTECTED]
</snip>
_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
