"William E. Kempf" <[EMAIL PROTECTED]> writes:
>> From: David Abrahams <[EMAIL PROTECTED]>
>> "William E. Kempf" <[EMAIL PROTECTED]> writes:
>>
>> >> From: David Abrahams <[EMAIL PROTECTED]>
>> >> "William E. Kempf" <[EMAIL PROTECTED]> writes:
>> >>
>> >> >> From: Martin Brown <[EMAIL PROTECTED]>
>> >> >>
>> >> >> 2. The user needs a localised error message.
>> >> > Is the textual representation of the exception name
>> >> > enough? If not, how do you propose a library
>> >> > provide such a localised error message?
>> >> I will weigh in here with one strong opinion:
>> >> producing localized error messages should not be the
>> >> job of the exception object or the code which throws
>> >> it. Error message formatting and localization should
>> >> happen after exceptions are caught.
>> >
>> > Full agreement. But what (if anything) must the
>> > exception object provide in order for the exception
>> > handlers to be able to format a localized message?
>>
>> You need to decide how much information you can give them.
>
> Uhmm... that's the question I've been asking.
What information do you *have* at the point of detection?
--
David Abrahams
[EMAIL PROTECTED] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
