File and line numbers in error messages

[Greg Hudson]

Ignore my previous answer.

On Wed, 2009-04-29 at 15:28 -0400, Sam Hartman wrote:
> I don't actually object to it, but grep seems like a
> better tool than cluttering up error messages that should be written
> for users.

I sort of lean in this direction myself; I suspect the counterargument
is that you have to guess what to grep for since the error message was
(in the general case) produced from a format string.

> Note that krb5_set_error_message is a public API (so it can be used in
> plugins) so you don't want to change its calling semantics or turn it
> into a macro.  I'd also argue that it would be bad if code built with
> this flag had a different ABI in terms of accessor or public exports
> than code built without this flag.

The idea is to have k5-int.h redefine uses of krb5_set_error_message to
use krb5_set_error_message_fl instead.  The old API will still be there,
unchanged.  Anyone who doesn't use k5-int.h will use the old API.