On Fri, Sep 9, 2016 at 11:38 AM, Jasper Lievisse Adriaanse <[email protected]> wrote: > Do we really want the filename to be printed in the message? If so we should > use __FILE__. On the other hand, having the function name makes more sense to > me.
This is a "not found" message in response to an explicit user command:
why does the user care what *source file* is generating that message?
arm and sparc64 do the Right Thing IMO:
if (p == NULL) {
(*pr)("not found\n");
return;
}
Philip Guenther
