Content deleted Content added
m Signing comment by Cantregistermynick - "→No any date per whole article.: new section" |
→Compiler support section: new section |
||
Line 105:
Alexander Ilyin 20:16, 4 July 2010 (UTC) <small><span class="autosigned">—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Cantregistermynick|Cantregistermynick]] ([[User talk:Cantregistermynick|talk]] • [[Special:Contributions/Cantregistermynick|contribs]]) </span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
== Compiler support section ==
The compiler support section says that "For a long time, the Microsoft Visual Studio family of compilers and tools and Borland's compilers were the only tools that could provide this" (meaning the ability to handle Win32 headers etc.).
In my recollection, this is not true. Before Visual Studio came out, there was Microsoft C/C++, but also Zortech C/C++, Watcom C++ and Turbo C++. Zortech C++ became Symantec C++, was dropped by them, and then bought back by its original author and survives to this day as Digital Mars C++. Watcom was withdrawn from the market before satisfactorily implementing the ARM-level language. Turbo C++ became Borland C++. I owned all three. Watcom and Symantec supplied "memory extenders" which allowed Win32 programs to run on Win16 with Microsoft's redistridutable "win32s" shim DLL. I can't remember why I switched from Borland to Watcom but I think it was because Borland lacked 32-bit support.
I think you'll find the Zortech compiler was the first usable C++ on Win32/Win16, before even Microsoft had one.
Towards the end of this era COM appeared and assumed a certain binary vtable layout. At least Zortech tracked this change. I don't accept that COM is part of Win32, by the way.
| |||