News for hackers. Stuff that matters.
Re:Writing C software without the standard library by imron on Tuesday November 29, 2016 @05:35AM (#13062196)
I've written Windows programs without the std library. The Win32 has plenty of replacement functions you can use instead though so it's much less work than what's presented here.

You get the same sorts of benefits though.

Re:Writing C software without the standard library by userbinator on Tuesday November 29, 2016 @06:23AM (#13062358)
Win32 is itself a layer on top of the syscalls, and already provides much of the functionality of the C standard library.
Re:Writing C software without the standard library by imron on Tuesday November 29, 2016 @07:33AM (#13062636)
Yes, that was partly my point.

You can get reduced executable size and a lack of dependencies on various msvc*.dlls, without giving up much of the functionality of the C standard library and without having to write it all yourself.

Re:Writing C software without the standard library by qb45 on Tuesday November 29, 2016 @08:40AM (#13062940)
Fine, but you get this thanks to already being linked with these megagodzillas like kernel32.dll. Try without them.
Re:Writing C software without the standard library by ekr on Tuesday November 29, 2016 @10:10AM (#13063454)
On windows nt, ntdll gets loaded in all processes, it's hardcoded in the kernel (http://gate.upm.ro/os/LABs/Windows_OS_Internals_Curriculum_R...). That's where the loader resides, so you can't go without it. And that's where all the Zw/Nt* functions/ i.e. where the syscalls are.

So you can't really go without it.

Re:Writing C software without the standard library by tubs on Tuesday November 29, 2016 @07:39PM (#13067506)
Except the new picoprocesses, which don't get ntdll (or anything really, I guess).
Re:Writing C software without the standard library by vertex-four on Tuesday November 29, 2016 @08:49AM (#13062982)
A program which isn't linked against the Win32 stuff is an invalid program, since syscalls in Windows are not at all stable.