about summary refs log tree commit diff
path: root/include/stdio.h
Commit message (Collapse)AuthorAgeFilesLines
* use a common definition of NULL as 0L for C and C++Rich Felker2013-01-181-6/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the historical mess of having different definitions for C and C++ comes from the historical C definition as (void *)0 and the fact that (void *)0 can't be used in C++ because it does not convert to other pointer types implicitly. however, using plain 0 in C++ exposed bugs in C++ programs that call variadic functions with NULL as an argument and (wrongly; this is UB) expect it to arrive as a null pointer. on 64-bit machines, the high bits end up containing junk. glibc dodges the issue by using a GCC extension __null to define NULL; this is observably non-conforming because a conforming application could observe the definition of NULL via stringizing and see that it is neither an integer constant expression with value zero nor such an expression cast to void. switching to 0L eliminates the issue and provides compatibility with broken applications, since on all musl targets, long and pointers have the same size, representation, and argument-passing convention. we could maintain separate C and C++ definitions of NULL (i.e. just use 0L on C++ and use (void *)0 on C) but after careful analysis, it seems extremely difficult for a C program to even determine whether NULL has integer or pointer type, much less depend in subtle, unintentional ways, on whether it does. C89 seems to have no way to make the distinction. on C99, the fact that (int)(void *)0 is not an integer constant expression, along with subtle VLA/sizeof semantics, can be used to make the distinction, but many compilers are non-conforming and give the wrong result to this test anyway. on C11, _Generic can trivially make the distinction, but it seems unlikely that code targetting C11 would be so backwards in caring which definition of NULL an implementation uses. as such, the simplest path of using the same definition for NULL in both C and C++ was chosen. the #undef directive was also removed so that the compiler can catch and give a warning or error on redefinition if buggy programs have defined their own versions of NULL prior to inclusion of standard headers.
* expose [v]asprintf under _BSD_SOURCERich Felker2012-12-281-2/+2
| | | | reported/requested by Strake; simplified from the provided patch
* feature test macros: make _GNU_SOURCE enable everythingRich Felker2012-12-031-3/+0
| | | | | | | | | | | | | | | | previously, a few BSD features were enabled only by _BSD_SOURCE, not by _GNU_SOURCE. since _BSD_SOURCE is default in the absence of other feature test macros, this made adding _GNU_SOURCE to a project not a purely additive feature test macro; it actually caused some features to be suppressed. most of the changes made by this patch actually bring musl in closer alignment with the glibc behavior for _GNU_SOURCE. the only exceptions are the added visibility of functions like strlcpy which were BSD-only due to being disliked/rejected by glibc maintainers. here, I feel the consistency of having _GNU_SOURCE mean "everything", and especially the property of it being purely additive, are more valuable than hiding functions which glibc does not have.
* default features: make musl usable without feature test macrosRich Felker2012-09-071-5/+1
| | | | | | | | | | the old behavior of exposing nothing except plain ISO C can be obtained by defining __STRICT_ANSI__ or using a compiler option (such as -std=c99) that predefines it. the new default featureset is POSIX with XSI plus _BSD_SOURCE. any explicit feature test macros will inhibit the default. installation docs have also been updated to reflect this change.
* use restrict everywhere it's required by c99 and/or posix 2008Rich Felker2012-09-061-28/+34
| | | | | | | | to deal with the fact that the public headers may be used with pre-c99 compilers, __restrict is used in place of restrict, and defined appropriately for any supported compiler. we also avoid the form [restrict] since older versions of gcc rejected it due to a bug in the original c99 standard, and instead use the form *restrict.
* implement "low hanging fruit" from C11Rich Felker2012-08-251-0/+2
| | | | | | | | based on Gregor's patch sent to the list. includes: - stdalign.h - removing gets in C11 mode - adding aligned_alloc and adjusting other functions to use it - adding 'x' flag to fopen for exclusive mode
* add bsd fgetln functionRich Felker2012-08-111-0/+4
| | | | | optimized to avoid allocation and return lines directly out of the stream buffer whenever possible.
* add prototypes for getw/putwRich Felker2012-07-041-0/+2
|
* _GNU_SOURCE is supposed to imply _LARGEFILE64_SOURCERich Felker2012-06-041-1/+1
| | | | | | | | | this is ugly and stupid, but now that the *64 symbol names exist, a lot of broken GNU software detects them in configure, then either breaks during build due to missing off64_t definition, or attempts to compile without function declarations/prototypes. "fixing" it here is easier than telling everyone to add yet another feature test macro to their builds.
* there is no such GNU function fpurge, only __fpurge.Rich Felker2012-05-281-1/+0
| | | | no idea where I got the idea fpurge should exist...
* add prototype for BSD/GNU stdio *_unlocked extension functionsRich Felker2012-05-281-2/+12
| | | | also fix up distinction of what is GNU-only and what's GNU+BSD
* remove duplicate lfs64 cruft in stdio.hRich Felker2012-05-281-2/+0
|
* support _BSD_SOURCE feature test macroRich Felker2012-05-221-4/+7
| | | | | patch by Isaac Dunham. matched closely (maybe not exact) to glibc's idea of what _BSD_SOURCE should make visible.
* add support for ugly *64 functions with _LARGEFILE64_SOURCERich Felker2012-05-041-0/+12
| | | | | | | | | | | | | | | | musl does not support legacy 32-bit-off_t whatsoever. off_t is always 64 bit, and correct programs that use off_t and the standard functions will just work out of the box. (on glibc, they would require -D_FILE_OFFSET_BITS=64 to work.) however, some programs instead define _LARGEFILE64_SOURCE and use alternate versions of all the standard types and functions with "64" appended to their names. we do not want code to actually get linked against these functions (it's ugly and inconsistent), so macros are used instead of prototypes with weak aliases in the library itself. eventually the weak aliases may be added at the library level for the sake of using code that was originally built against glibc, but the macros will still be the desired solution in the headers.
* add prototypes for GNU *_unlocked stdio functionsRich Felker2011-09-111-0/+4
| | | | | | | actually these are just weak aliases for the normal locking versions right now, and they will probably stay that way since making them lock-free without slowing down the normal versions would require significant code duplication for no benefit.
* implement fmemopenRich Felker2011-09-031-0/+1
| | | | testing so far has been minimal. may need further work.
* implement open_memstreamRich Felker2011-09-031-0/+1
| | | | | this is the first attempt, and may have bugs. only minimal testing has been performed.
* implement the nonstandard GNU function fpurgeRich Felker2011-06-301-0/+1
| | | | | | this is a really ugly and backwards function, but its presence will prevent lots of broken gnulib software from trying to define its own version of fpurge and thereby failing to build or worse.
* add more legacy functions: setlinebuf and setbufferRich Felker2011-04-051-0/+2
|
* prototypes for GNU asprintf/vasprintfRich Felker2011-02-201-0/+2
|
* move stdio stuff that's not arch-specific out of bitsRich Felker2011-02-151-1/+9
|
* begin namespace-cleanup of standard C headersRich Felker2011-02-141-20/+31
|
* initial check-in, version 0.5.0 v0.5.0Rich Felker2011-02-121-0/+144