Displaying 3 results from an estimated 3 matches for "bfprintf".
Did you mean:
fprintf
2016 Apr 04
1
Re: [PATCH 2/2] Use 'error' function for fprintf followed by exit.
...ex than the previous commit because we must be
> careful to:
>
> - Remove the program name (since error(3) prints it).
>
> - Remove any trailing \n character from the message.
>
> Candidates for replacement were found using:
>
> pcregrep --buffer-size 10M -M '\bfprintf\b.*\n.*\bexit\b' `git ls-files`
> ---
Really nice improvement -- just a couple of notes.
> @@ -130,10 +131,8 @@ main (int argc, char *argv[])
> int r;
>
> g = guestfs_create ();
> - if (g == NULL) {
> - fprintf (stderr, _("guestfs_create: failed to create...
2016 Apr 04
0
[PATCH 2/2] Use 'error' function for fprintf followed by exit.
...ve fixed that).
It's slightly more complex than the previous commit because we must be
careful to:
- Remove the program name (since error(3) prints it).
- Remove any trailing \n character from the message.
Candidates for replacement were found using:
pcregrep --buffer-size 10M -M '\bfprintf\b.*\n.*\bexit\b' `git ls-files`
---
align/scan.c | 7 +-
cat/cat.c | 16 ++--
cat/filesystems.c | 24 +++---
cat/log.c | 17 ++--
cat/ls.c...
2016 Apr 04
2
[PATCH 1/2] Use 'error' function consistently throughout.
Wherever we had code which did:
if (something_bad) {
perror (...);
exit (EXIT_FAILURE);
}
replace this with use of the error(3) function:
if (something_bad)
error (EXIT_FAILURE, errno, ...);
The error(3) function is supplied by glibc, or by gnulib on platforms
which don't have it, and is much more flexible than perror(3). Since
we already use error(3), there seems to be