QuickC for Windows - Revision history

Flx: capitalize DOS & whitespace

2024-02-06T15:34:51Z

capitalize DOS & whitespace

Jnc: Update cat

2018-10-19T11:26:00Z

Update cat

Jnc: avoid redir

2017-08-07T14:00:18Z

avoid redir

Neozeed at 22:05, 3 August 2010

2010-08-03T22:05:58Z

Neozeed at 22:05, 3 August 2010

2010-08-03T22:05:24Z

Neozeed at 21:20, 3 August 2010

2010-08-03T21:20:36Z

Neozeed: minor additions

2010-05-25T08:32:01Z

minor additions

Neozeed at 19:39, 23 May 2010

2010-05-23T19:39:13Z

Neozeed at 18:56, 14 April 2010

2010-04-14T18:56:11Z

Neozeed at 01:57, 26 October 2009

2009-10-26T01:57:56Z

@@ Line 10: / Line 10: @@
 }}
-QuickC for Windows was a [[C (language)|C]] [[compiler]] hosted in [[Microsoft Windows 3.0]].  This was the cheapest way of writing [[protected mode]] [[program]]s, 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.
+QuickC for Windows was a [[C (language)|C]] [[compiler]] hosted in [[Microsoft Windows 3.0]]. This was the cheapest way of writing [[protected mode]] [[program]]s, 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.
+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 static libraries.  There is support for creating Windows DLL's however you cannot call the QuickWin functions from those DLL's.  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 static libraries. There is support for creating Windows DLL's however you cannot call the QuickWin functions from those DLL's. 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 in the [http://books.google.com/books?id=Bj4EAAAAMBAJ&lpg=PA4&pg=PA113#v=onepage&q&f=false InfoWorld Nov 18, 1991].

@@ Line 10: / Line 10: @@
 }}
-QuickC for Windows was a [[C (language)|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.
+QuickC for Windows was a [[C (language)|C]] [[compiler]] hosted in [[Microsoft Windows 3.0]].  This was the cheapest way of writing [[protected mode]] [[program]]s, 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.
+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.
+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 static libraries.  There is support for creating Windows DLL's however you cannot call the QuickWin functions from those DLL's.  The compiler is a DLL called from the interface, so you cannot invoke any of it from the command line.
@@ Line 20: / Line 20: @@
 A good review is available in the [http://books.google.com/books?id=Bj4EAAAAMBAJ&lpg=PA4&pg=PA113#v=onepage&q&f=false InfoWorld Nov 18, 1991].
-[[Category:C compilers]]
+{{semi-stub}}
-{{stub}}

@@ Line 10: / Line 10: @@
 }}
-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.
+QuickC for Windows was a [[C (language)|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.

@@ Line 1: / Line 1: @@
-{{Infobox C compilers
+{{Infobox Software
 | image = QuickC front.jpg|150px
 | caption = A retail copy of QuickC for Windows
@@ Line 20: / Line 20: @@
 A good review is available in the [http://books.google.com/books?id=Bj4EAAAAMBAJ&lpg=PA4&pg=PA113#v=onepage&q&f=false InfoWorld Nov 18, 1991].
+[[Category:C compilers]]
 {{stub}}

@@ Line 1: / Line 1: @@
-{{Infobox Software
+{{Infobox C compilers
 | image = QuickC front.jpg|150px
 | caption = A retail copy of QuickC for Windows
@@ Line 20: / Line 20: @@
 A good review is available in the [http://books.google.com/books?id=Bj4EAAAAMBAJ&lpg=PA4&pg=PA113#v=onepage&q&f=false InfoWorld Nov 18, 1991].
-[[Category:C compilers]]
 {{stub}}

@@ 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.
 [[Category:Compilers]]
 {{stub}}

@@ Line 5: / Line 5: @@
 | creator = Microsoft
 | year introduced = 1990
-| architecture = [[i286]], [[i386]]
+| architecture = [[i8086]], [[i286]]
 | type = Compiler
 | language = C
 }}
-The interface from QuickC for windows eventually found its way into the Visual C++ program, as both share many common elements.
+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.
-You could target both MS-DOS & Windows 3.0 with this compiler.
+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.
 [[Category:Compilers]]
 {{stub}}