Olaf Titz wrote:
>
> But I just found another, more severe reason against printk: gcc
> woudln't know how to check the new types.
Yes. Implementing it within vsprintf() is really nice - about four
lines of code (call sprintf() recursively) and fully reentrant.
But gcc will warn, and there's no way to prevent it. This is a
showstopper.
Even if you cook up a new (non-%) token it will still complain because
of the extra args.
The only solution I can think of is to create a new function
'printk_on_steroids()' and _not_ tell gcc that it takes printf-style
args.
-- -akpm-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:12 EST