Copy stable/10@r272459 to releng/10.1 as part of
the 10.1-RELEASE process.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Clarify that the ' flag is an apostrophe.

MFC after: 2 weeks

- Fix the claim that the output is always null-terminated. This isn't
true if the size is zero.
- Fix a claim that sprintf() is the same as snprintf() with an
infinite size. It's equivalent to snprintf() with a size of
INT_MAX + 1.
- Document the return values in the return values section.
- Document the possible errno value of EOVERFLOW.

MFC after: 2 weeks

Revert changes of 'assure' to 'ensure' made in r211936.

Approved by: rrs (mentor)

Fix incorrect usage of 'assure' and 'insure'.

Approved by: rrs (mentor)

mdoc: move CAVEATS, BUGS and SECURITY CONSIDERATIONS sections to the
bottom of the manpages and order them consistently.

GNU groff doesn't care about the ordering, and doesn't even mention
CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put
them.

Found by: mdocml lint run
Reviewed by: ru

mdoc: use macro for +- that is understood by mdocml

Reviewed by: brueffer

I feel this wording of the history is more clear.
ANSIfy vasprintf() while I'm here.

%U was macroized in mdoc(7), escape.

Fix the dprintf() prototype.

PR: 141087
Submitted by: Jeremy Huddleston <jeremyhu@apple.com>
MFC after: 3 days

Add dprintf() and vdprintf() from POSIX.1-2008. Like getline(),
dprintf() is a simple wrapper around another function, so we may as
well implement it. But also like getline(), we can't prototype it by
default right now because it would break too many ports.

Update the manpage to reflect r145172.

Updates for changes in the way printf() handles hex floating point
numbers.

Per Regents of the University of Calfornia letter, remove advertising
clause.

# If I've done so improperly on a file, please let me know.

Remove references to nonexistent "FreeBSD Security Architecture" document.

Document that the length modifier l is ignored for floating point
conversion specifiers (a, A, e, E, f, F, g and G).

Markup, grammar, and spelling fixes.

Bring the *printf(3) documentation up to date with the code:

- Update and improve the documentation for %[aA]
o Like %[eE], %[aA] may round the result if a precision is specified.
o Grammar police: Fix a split infinitive.
o The FreeBSD implementation does better than the minimum required
by C99 (literal translation of the mantissa). The digit before
the hexadecimal-point is never 0 unless the number itself is 0.
o Clarify that the exponent field represents a decimal exponent of 2.
o Discuss the fact that multiple valid representations are possible.
o Remove the entry in the BUGS section claiming that %[aA] is not
implemented.

- Remove the entry in the BUGS section claiming that the ' flag for
printing thousands separators is unimplemented for floating-point.

- Remove the entry in the BUGS section claiming that the L modifier
reduces the precision to "double" before conversion.

Note that the printf(3) and scanf(3) family of functions don't deal with
multibyte characters in the format string correctly.

Document the fact that the printf() family of functions return negative
values (EOF in our case) on error, and some of the possible errno values
in an Errors section.

PR: 39257

mdoc(7) police: "The .Fn function".

Consistently mark std(in|out|err) with .Dv, because that's how they
are marked up in stdio(3), and because they are defined expressions
of type "FILE *".

Approved by: re

Cross-reference fmtcheck(3).

Indent code example with one tab, not two, for consistency with the rest.

Add cross-references between wide character and single-byte character
versions of printf() and scanf().

Implement the %ls and %lc conversions for printing wide character strings
and wide characters. These were already documented in the manual page,
with an entry mentioning that they were not implemented yet. The XSI
%S and %C synoyms have not been added.

Style: One space between "restrict" qualifier and "*".

- For compliance with IEEE Std 1003.1-2001, add the 'restrict'
qualifier to function prototypes and definitions where
appropriate using the '__restrict' macro.
- Update the manual page.

- Introduce the 'restrict' qualifier to function prototypes and
definitions to comply with IEEE Std 1003.1-2001.
- Update the manual pages.

Fix typos; each file has at least one s/seperat/separat/
(I skipped those in contrib/, gnu/ and crypto/)
While I was at it, fixed a lot more found by ispell that I
could identify with certainty to be errors. All of these
were in comments or text, not in actual code.

Suggested by: bde
MFC after: 3 days

mdoc(7) police: punctuation.

Don't claim to fully implement C99 in the STANDARDS section and then disclaim
compliance in the BUGS section immediately below.

Fix style and wording bugs introduced in my last commit.

Sponsored by: DARPA, NAI Labs

o Move more information from BUGS into SECURITY CONSIDERATIONS and
condense the redundant bits.
o Provide an example for using snprintf over sprintf. This may be
supplemented with an asprintf() example soon.

Sponsored by: DARPA, NAI Labs

Include information on the dangers of passing a user-supplied string as
a format string. This will later on be changed to a reference to the
FreeBSD Security Architecture after it has been committed.

PR: docs/39320
Sposnored by: DARPA, NAI Labs

mdoc(7) police:

Stop abusing the .%J macro for where the .Pa macro should have been used.

Add new "SECURITY CONSIDERATIONS" sections.

Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs

mdoc(7) police: Minor formatting nits and optimizations to rev. 1.34.

Remove blank line.

Implement several of the c99 updates to printf(3):
- New length modifiers: hh, j, t, z.
- New flag: '. Note that %'f is not yet implemented.
- Use "inf"/"nan" for efg formats, "INF"/"NAN" for EFG formats.
- Implemented %q in terms of %ll; if "quad_t" is not "long long"
%q will break.

Still to do:
- %C, %S, %lc, %ls (wide character support)
- %'f (thousands in integer portion of %f)
- %a/%A (exact hex representation of floating-point numbers)

Garrett Wollman wrote the first version of the vfprintf.c update;
Mike Barcroft wrote the first version of the printf.3 changes.

mdoc(7) police: Use the new .In macro for #include statements.

mdoc(7) police: fixed/simplified formatting.

Add description for the 'll' modifier for long long. In essence a copy
from the 'l' description with s/long/long long/g.

PR: 27017
Submitted by: Guy Harris <guy@alum.mit.edu>
MFC after: 2 weeks

Back out my changes describing how snprintf nul terminates. It
was from the iso standard. Keep the sentence that says it is always
NUL terminated to make sure that people understand that.

Requested by: bde

Minor improvements:
o Explain snprintf's return value better.
o Document snprintf, et al, were defined in C-99
o Warn against %n.

Correct the documentation for snprintf() and vsprintf() which actually
return the number of characters that would have been in the new string.

Obtained from: OpenBSD
MFC after: 3 days

Add warnings about trusting user-supplied data.

Reviewed by: ru
Approved by: murray
Obtained from: OpenBSD

mdoc(7) police: fix markup.

.St -ansiC -> .St -isoC

mdoc(7) police: mark LC_NUMERIC with .Dv.

Note that decimal point taken from locale (SUSv2)

mdoc(7) police: split punctuation characters + misc fixes.

Make it a bit clearer that asprintf doesn't actually "return" a pointer in
the normal sense of the word, but does it through one of its arguments which
is a pointer to a pointer.

PR: 23717
Submitted by: phk

Prepare for mdoc(7)NG.

Avoid use of direct troff requests in mdoc(7) manual pages.

Introduce ".Lb" macro to libc manpages.

More libraries manpages updates following.

Remove more single-space hard sentence breaks.

Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.

We no longer care about the VAX and Tahoe compilers :-)

$Id$ -> $FreeBSD$

Fixed missing "G" in the list item for the main description of %g and
%G formats.

asprintf() does use realloc() internally, but saying so in the manpage can be
misinterpreted to mean that the pointer passed to asprintf() must be suitable
for passing to realloc() as-is (ie. either a NULL pointer or a valid pointer).

Add $Id$, to make it simpler for members of the translation teams to
track.

The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;

.\" $Id$
.\"

If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.

Approved by: bde

Replace my original asprintf() and vasprintf() hacks with something
more cleanly integrated with stdio. This should be faster and cleaner
since it doesn't memcpy() the data into a seperate buffer. This lets
stdio allocate and manage the buffer and then hand it over to the user.

Obtained from: Todd Miller <Todd.Miller@courtesan.com> via OpenBSD

Spelling corrections.

PR: 6868
Submitted by: Josh Gilliam <josh@quick.net>

FIxed arg types (mostly missing consts) in synopsis.

The following patch to lib/libc/stdio implements positional arguments in
a manner consistent with other implementations. Its done in a way that
adds only a tiny amount of overhead when positional arguments are not used.
I also have a test program to go with this, but don't know where it belongs
in the tree.

Submitted-By: Bill Fenner <fenner@FreeBSD.ORG>

Update some more man pages to use the .Fx macro.

Reword the sentence about the required space for the result string.

Closes PR # 1303.-

Add an implementation of the gnu-ish asprintf() and vasprintf(). They are
not based on gpl'ed code, just prototype and usage. I'm not 100% certain
they behave the same while the system is in trouble (eg: malloc() failing)
but in those circumstances all bets would be off anyway.

These routines work like sprintf() and vsprintf(), except that instead of
using a fixed buffer, they allocate memory and return it to the user
and it's the user's responsibility to free() it. They have allocate as
much memory as they need (and can get), so the size of strings it can deal
with is limited only by the amount of memory it can malloc() on your
behalf.

There are a few gpl'ed programs starting to use this interface, and it's
becoming more common with the scares about security risks with sprintf().
I dont like the look of the code that the various programs (including
cvs, gdb, libg++, etc) provide if configure can't find it on the system.

It should be possible to modify the stdio core code to provide this
interface more efficiently, I was more worried about having something
that worked and was secure. :-) (I noticed that there was once intended
to be a smprintf() routine when our stdio was written for 4.4BSD, but it
looks pretty stillborn, and it's intended interface is not clear). Since
Linux and gnu libc have this interface, it seemed silly to bring yet
another one onto the scene.

Correct a minor typo. Fixes part of PR#1000.

Submitted by: Dave Glowacki <dglo@ssec.wisc.edu>

Fixed typo.

This commit was generated by cvs2svn to compensate for changes in r1573,
which included commits to RCS files with non-trunk default branches.

BSD 4.4 Lite Lib Sources