The Microsoft C standard library implementation also takes this approach - C++ implementation with C exports, for the reasons called out by the sibling comments.
That does not always necessarily follow. The VC runtime, for the C portion of the library, is now written in C++ internally.
Windows has moved to an evergreen OS model: http://blogs.windows.com/bloggingwindows/2015/01/21/the-next...
Interestingly enough, it wasn't $future_version, but version 1.0, that didn't even support .NET and was scriptable only through JS. Silverlight is still scriptable through JS to this day. Given that Silverlight already…
That's probably the issue with the JS standard they discuss here: http://blogs.msdn.com/b/ie/archive/2010/07/16/how-ie9-platfo...
The Vatican started doing that millenia after there were no native populations of latin-speakers left.
why not R6RS?
FolderShare was acquired. I don't know if Microsoft has done a terrible lot with the program since the acquisition to be able to claim the success as its own.
The Microsoft C standard library implementation also takes this approach - C++ implementation with C exports, for the reasons called out by the sibling comments.
That does not always necessarily follow. The VC runtime, for the C portion of the library, is now written in C++ internally.
Windows has moved to an evergreen OS model: http://blogs.windows.com/bloggingwindows/2015/01/21/the-next...
Interestingly enough, it wasn't $future_version, but version 1.0, that didn't even support .NET and was scriptable only through JS. Silverlight is still scriptable through JS to this day. Given that Silverlight already…
That's probably the issue with the JS standard they discuss here: http://blogs.msdn.com/b/ie/archive/2010/07/16/how-ie9-platfo...
The Vatican started doing that millenia after there were no native populations of latin-speakers left.
why not R6RS?
FolderShare was acquired. I don't know if Microsoft has done a terrible lot with the program since the acquisition to be able to claim the success as its own.