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 18:57:14

https://bugzilla.kernel.org/show_bug.cgi?id=55371
--- Comment #8 from Filipus Klutiero <chealer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Few students will be given man printf to read in school. The vast majority of
consultations will happen when people try to interpret or write a call to
printf(). It is unlikely that these readers will read the entire page at once.

If the documentation says each conversion specifier asks for the next argument,
it is reasonable to expect that readers - whether careful or not - will
conclude that each conversion specifier asks for the next argument, unless they
read up to the point where this is contradicted.

If you think a note about exceptions would clutter, terminology can be used,
for example "regular conversion specifier" versus "special conversion
specifier".

-- 
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