3 ms·
If we're being pedantic here, it's not Win32. > (Note that this was formerly called the Win32 API. The name Windows API more accurately reflects its roots in 1
by ziml77 6y ago
If we're being pedantic here, it's not Win32.
> (Note that this was formerly called the Win32 API. The name Windows API more accurately reflects its roots in 16-bit Windows and its support on 64-bit Windows.)
Though Win32 is going to stick around for a while as can be seen in the URL for the page that's quoted from: https://docs.microsoft.com/en-us/windows/win32/apiindex/windows-api-list https://docs.microsoft.com/en-us/windows/win32/apiindex/wind...
- a-dub 6y agoi think it's still called win32 today because win32 was a massive overhaul. 16 bit windows was loaded with that far and near pointer gunk to stretch those 16 bit pointers which win32 was able to do away with thanks to larger pointer widths. regarding win32 vs. the nt api. i'm not super familiar with the pedantic distinctions there, but i do know, much to the programmer's chagrin, the thousands of windows api functions have varying levels of kernel entry, where i always have appreciated the (relatively) small number of unix style syscalls and the clear delineation between kernel and userspace api. (although i suppose futexes blur that, in name at least!)
- Joker_vD 6y agoWell, since introduction of vsyscall and vDSO, the Linux syscalls too have varying levels of kernel entry.