On 2/12/2019 11:44 AM, Jens Axel Søgaard wrote:
FWIW here is the readme describing how to build libraries for Windows: https://github.com/racket/racket/tree/master/racket/src/native-libs
That is a guide useful in general, but it doesn't answer my question to Philip. Plain C DLLs are (for the most part) build-chain agnostic, but non-C DLLs can provide C callable functions, and Visual Studio can create some types of non-C DLLs that GCC can't.
20 years hence, Microsoft's C compiler isn't even fully C90 compliant. They've stated publicly that full C90 compliance will not be achieved and C99 and later won't be addressed except for features specifically needed by "major customers".
They seem to care much more about C++ compliance than C. They are (AFAIK) fully compliant with C++03. They aren't fully compliant with C++11 or later, but they are much closer to compliance with the C++ standards than they are with C.
George -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
