RE: [lwip-devel] %#p in some traces

[Bill Auerbach]

The behavior is undefined, so it wouldn't be technically legal (or
portable).  I would make the assumption that a # on a format that library
didn't handle would be ignored.  It's after the % and before the format
specifier so it can't really be output with the data.

I see Kieran's reply too - these #'s caused compiler errors or warnings?  A
compiler that is doing more than it is defined to do and is checking the
semantics of arguments to functions is doing this by compiler extension.
Removing these #'s isn't much different than changing source code for
compiler bugs.  Do we want to be changing source code for compiler
extensions too?

Bill

>-----Original Message-----
>Is the # legal for all compilers inside %p ? I'm not sure about when I
>read that :
>
>http://www.opengroup.org/onlinepubs/9699919799/functions/printf.html