| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Notes:
svn path=/head/; revision=56131
|
| |
|
|
| |
Notes:
svn path=/head/; revision=50476
|
| |
|
|
|
|
|
| |
%G formats.
Notes:
svn path=/head/; revision=49518
|
| |
|
|
|
|
|
|
| |
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).
Notes:
svn path=/head/; revision=49082
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=48794
|
| |
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=37487
|
| |
|
|
|
|
|
|
| |
PR: 6868
Submitted by: Josh Gilliam <josh@quick.net>
Notes:
svn path=/head/; revision=36692
|
| |
|
|
| |
Notes:
svn path=/head/; revision=24008
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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>
Notes:
svn path=/head/; revision=21674
|
| |
|
|
| |
Notes:
svn path=/head/; revision=17763
|
| |
|
|
|
|
|
| |
Closes PR # 1303.-
Notes:
svn path=/head/; revision=16241
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=15931
|
| |
|
|
|
|
|
| |
Submitted by: Dave Glowacki <dglo@ssec.wisc.edu>
Notes:
svn path=/head/; revision=15164
|
| |
|
|
| |
Notes:
svn path=/head/; revision=8534
|
|
|
Notes:
svn path=/cvs2svn/branches/unlabeled-1.1.1/; revision=1573
|
