I was just reading DJB's daemontools (less than 6K LOC, very tidy!), and he doesn't use libc. Actually his code has been collected in libdjb, which seems quite nice:
And also the Plan 9 / Go guys don't use ANSI libc as far as I remember.
Those are two examples of people who don't even use the ANSI libc interface. But there are plenty of people who don't use GNU libc, and use uclibc or various other source-compatible alternatives. I think Debian switched to eglibc awhile ago.
[1] - https://groups.google.com/forum/#!msg/golang-nuts/H-NTwhQVp-...
http://code.google.com/p/go/source/browse/include/libc.h
Which is definitely not ANSI libc. Go programmers won't care about this, because it's an implementation detail, but we're talking about reading source code.
It's a public domain C library, much smaller and less of a monster than glibc, plus you don't have to worry about any implications of reading GPL code.
Unfortunately, for C this is pretty hard to do, at least for the GNU libc. I'm not trying to critique the implementation, but every time I dive in (generally to help someone on Stack Overflow) I'm confused and get to spend a lot of time searching the code.
It's obviously optimized for a great deal of other parameters before ease of reading, which I totally understand yet still am a bit sorry to see.