On Fri, Sep 9, 2016 at 3:19 PM, Jasper Lievisse Adriaanse <[email protected]> wrote: > On Fri, Sep 09, 2016 at 01:54:46PM -0700, Philip Guenther wrote: >> 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? > I have no idea why the user would care about the source file. However the > function triggering it might be of some more information, albeit of dubious > added value. Perhaps the message should be normalized across the board > following arm/sparc64?
In a word: YES.
