That is an incredibly poor idea that will break any program that
relies on the published error code. If you really feel strongly about
the precise wording for what is almost certainly a bone-numbing stupid
programmer error, make up a secondary error code. That's what they're
there for.

On 10/14/2010 5:03 AM, Dmitry Yemanov wrote:
> Dimitry Sibiryakov wrote:
>
>> In this case I would suggest to change error message to something more precise.
>> "Invalid handle" doesn't make enough information for decision-making. "Dirty input handle"
>> sounds good enough.
> The problem is that the same error code is used for both non-NULL handle
> during creating the object and invalid (NULL or unknown) handle during
> operating with the object. I don't see how changing the message text
> would still be understandable for both kinds of error. Instead, I'd
> introduce new error codes with appropriate messages.
>
>
> Dmitry
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


--
Jim Starkey
Founder, NimbusDB, Inc.
978 526-1376