Gregory's Server@bagder Don't leave us hanging, what kind of weirdnesses, quirkynesses or special cases are the most egregious? We need examples!
|
7 comments
 @DubioserKerl @bagder there is one but it's not following the standard specification when Microsoft decides the standard is wrong. Which they do more often than other systems.  @DubioserKerl @bagder libc versions on Windows are actually a part of the compiler instead of a fundamental system component like on Linux. This means the MSVC version you use determines the libc version you ship (either statically linking it, or relying on those VC++ redistributables). This is actually a good thing compared to Linux, because it allows cleaner separation between modules. This is a problem for Flatpak etc on Linux wrt graphics drivers.  @bagder @DubioserKerl As long as you're not using native (\\?\) paths, / works fine as path separator. But yes to everything else. @bagder @DubioserKerl with "no std libc" do you mean that it's not standards compliant like another user pointed out? |
@DubioserKerl everything from path separators, stupid shells, charsets, to not excepting non-sockets in select, no std libc, ownershipd of memory passed to DLLs, ...