Thread (1 message) 1 message, 1 author, 2015-05-05

[Bug 55371] printf: a conversion specifier doesn't necessarily ask for an argument

From: <hidden>
Date: 2015-05-05 16:05:17

https://bugzilla.kernel.org/show_bug.cgi?id=55371

Filipus Klutiero [off-list ref] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|CODE_FIX                    |---
--- Comment #6 from Filipus Klutiero <chealer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Please do not close this ticket until the issue has been solved.

A simple patch for this issue is trivial - just rectify that only some
conversion specifiers ask for the next arguments, for example:

By default, the arguments are used in the order given, where each '*' and each
conversion specifier (except for some) asks for the next argument (and it is an
error if insufficiently many arguments are given).


A patch which would keep the current sentence's precision would have to list
the exceptions.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help