2011-04-05 15:16:49 +00:00
|
|
|
#ifndef _ERR_H
|
|
|
|
|
#define _ERR_H
|
|
|
|
|
|
2012-09-08 22:16:33 +00:00
|
|
|
#include <features.h>
|
2011-04-05 15:16:49 +00:00
|
|
|
#include <stdarg.h>
|
|
|
|
|
|
|
|
|
|
#ifdef __cplusplus
|
|
|
|
|
extern "C" {
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
void warn(const char *, ...);
|
|
|
|
|
void vwarn(const char *, va_list);
|
|
|
|
|
void warnx(const char *, ...);
|
|
|
|
|
void vwarnx(const char *, va_list);
|
|
|
|
|
|
further use of _Noreturn, for non-plain-C functions
note that POSIX does not specify these functions as _Noreturn, because
POSIX is aligned with C99, not the new C11 standard. when POSIX is
eventually updated to C11, it will almost surely give these functions
the _Noreturn attribute. for now, the actual _Noreturn keyword is not
used anyway when compiling with a c99 compiler, which is what POSIX
requires; the GCC __attribute__ is used instead if it's available,
however.
in a few places, I've added infinite for loops at the end of _Noreturn
functions to silence compiler warnings. presumably
__buildin_unreachable could achieve the same thing, but it would only
work on newer GCCs and would not be portable. the loops should have
near-zero code size cost anyway.
like the previous _Noreturn commit, this one is based on patches
contributed by philomath.
2012-09-07 03:34:10 +00:00
|
|
|
_Noreturn void err(int, const char *, ...);
|
|
|
|
|
_Noreturn void verr(int, const char *, va_list);
|
|
|
|
|
_Noreturn void errx(int, const char *, ...);
|
|
|
|
|
_Noreturn void verrx(int, const char *, va_list);
|
2011-04-05 15:16:49 +00:00
|
|
|
|
|
|
|
|
#ifdef __cplusplus
|
|
|
|
|
}
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#endif
|
