QuickC for Windows - Revision history

Flx: capitalize DOS & whitespace

2024-02-06T15:34:51Z

capitalize DOS & whitespace

← Older revision		Revision as of 15:34, 6 February 2024
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.		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].		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].

Jnc: Update cat

2018-10-19T11:26:00Z

Update cat

← Older revision		Revision as of 11:26, 19 October 2018
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.		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].		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}}~~
			[[Category: C Compilers]]

Jnc: avoid redir

2017-08-07T14:00:18Z

avoid redir

← Older revision		Revision as of 14:00, 7 August 2017
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.		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.

Neozeed at 22:05, 3 August 2010

2010-08-03T22:05:58Z

← Older revision		Revision as of 22:05, 3 August 2010
Line 1:		Line 1:
	{{Infobox ~~C compilers~~		{{Infobox Software
	\| image = QuickC front.jpg\|150px		\| image = QuickC front.jpg\|150px
	\| caption = A retail copy of QuickC for Windows		\| 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].		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}}		{{stub}}

Neozeed at 22:05, 3 August 2010

2010-08-03T22:05:24Z

← Older revision		Revision as of 22:05, 3 August 2010
Line 1:		Line 1:
	{{Infobox ~~Software~~		{{Infobox C compilers
	\| image = QuickC front.jpg\|150px		\| image = QuickC front.jpg\|150px
	\| caption = A retail copy of QuickC for Windows		\| 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].		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}}		{{stub}}

Neozeed at 21:20, 3 August 2010

2010-08-03T21:20:36Z

← Older revision		Revision as of 21:20, 3 August 2010
Line 1:		Line 1:
	{{Infobox OS		{{Infobox Software
	\| image = QuickC front.jpg\|150px		\| image = QuickC front.jpg\|150px
	\| caption = A retail copy of QuickC for Windows		\| caption = A retail copy of QuickC for Windows

Neozeed: minor additions

2010-05-25T08:32:01Z

minor additions

← Older revision		Revision as of 08:32, 25 May 2010
Line 16:		Line 16:
	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 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 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 [http://books.google.com/books?id=Bj4EAAAAMBAJ&lpg=PA4&pg=PA113#v=onepage&q&f=false ~~here~~].		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:~~Compilers~~]]		[[Category:C compilers]]
	{{stub}}		{{stub}}

Neozeed at 19:39, 23 May 2010

2010-05-23T19:39:13Z

← Older revision		Revision as of 19:39, 23 May 2010
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}}

Neozeed at 18:56, 14 April 2010

2010-04-14T18:56:11Z

← Older revision		Revision as of 18:56, 14 April 2010
Line 5:		Line 5:
	\| creator = Microsoft		\| creator = Microsoft
	\| year introduced = 1990		\| year introduced = 1990
	\| architecture = [[~~i286~~]], [[~~i386~~]]		\| architecture = [[i8086]], [[i286]]
	\| type = Compiler		\| type = Compiler
	\| language = C		\| language = C
	}}		}}
	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.

	~~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.

			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.

	[[Category:Compilers]]		[[Category:Compilers]]
	{{stub}}		{{stub}}

Neozeed at 01:57, 26 October 2009

2009-10-26T01:57:56Z

← Older revision		Revision as of 01:57, 26 October 2009
Line 9:		Line 9:
	\| language = C		\| language = C
	}}		}}
	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.		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.

	The interface from QuickC for windows eventually found its way into the Visual C++ program, as both share many common elements.		The interface from QuickC for windows eventually found its way into the Visual C++ program, as both share many common elements.