Difference between revisions of "QuickC for Windows"
| Line 17: | Line 17: | ||
The few restrictions is that you cannot create libraries (static, or dynamic). The compiler is a DLL called from the interface, so you cannot invoke any of it from the command line. | The few restrictions is that you cannot create libraries (static, or dynamic). The compiler is a DLL called from the interface, so you cannot invoke any of it from the command line. | ||
| + | |||
| + | A good review is available [http://books.google.com/books?id=Bj4EAAAAMBAJ&lpg=PA4&pg=PA113#v=onepage&q&f=false here]. | ||
[[Category:Compilers]] | [[Category:Compilers]] | ||
{{stub}} | {{stub}} | ||
Revision as of 20:39, 23 May 2010
| QuickC for Windows | |
 A retail copy of QuickC for Windows | |
| Type: | Compiler |
|---|---|
| Creator: | Microsoft |
| Architecture: | i8086, i286 |
| Date Released: | 1990 |
QuickC for Windows was a C compiler hosted in Microsoft Windows 3.0. This was the cheapest way of writing protected mode programs, as this retailed for $149, along with the $150 cost of Windows 3.0. Dos Extenders of the time with compilers cost several thousand dollars. Not only was this a super cheap solution, but the superior winhelp help engine made programming easier.
The interface from QuickC for windows eventually found its way into the Visual C++, as both share many common elements. What had started as an entry level compiler, was to give rise to the next generation tools.
You could target both MS-DOS & Windows 3.0 with this compiler, although the MS-DOS programs were restricted to real mode only. There was no dos extender support. However with the QuickWin library, it was desirable to port simple command line/text programs to Windows in order to use the additional memory.
The few restrictions is that you cannot create libraries (static, or dynamic). The compiler is a DLL called from the interface, so you cannot invoke any of it from the command line.
A good review is available here.
