Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!evax!utacfd!letni!rwsys!spudge!johnm
From: johnm@spudge.UUCP (John Munsch)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Books on Borland C++ and Windows
Message-ID: <28289@spudge.UUCP>
Date: 14 Mar 91 20:23:54 GMT
References: <27381@uflorida.cis.ufl.EDU>
Reply-To: johnm@spudge.UUCP (John Munsch)
Organization: Friends of Guru Bob
Lines: 33

In article <27381@uflorida.cis.ufl.EDU> jdb@reef.cis.ufl.edu (Brian K. W. Hook) writes:
>Well, I've been toying with the new Borland C++ 2.0 and Windows 3.0, and I
>have been having one BITCH of a time.

Sorry to hear that.  I'll try to help.

>I have Peter Norton's Power Guide to Windows Programming and the Microsoft
>Press Guide to Programming Windows, and these have plenty of code examples,
>however I need MUCH more information on using Borland C++ for setting up my
>.DEF, .RC, .C, .PRJ, .MAK, etc. files, then compiling correctly, defining
>the correct EXPORTS, etc.

Okay... Let's tackle these in order.
	1) .DEF - Unless you are doing something unusual you don't need one
	with Borland C++.  You can set the heap size, etc from the options
	menu and you don't need a .DEF for exports so just skip it.
	2) .RC  - Again, skip it.  Most of what you are doing can be more
	easily done directly to a .RES file with the Whitewater Resource
	Toolkit.
	3) .PRJ & .MAK - This is pretty much an either/or situation.  If you
	are using the IDE then you will want .PRJ files, otherwise you will
	use a .MAK file.  Perhaps a more specific question would help here.
	4) EXPORTS - Don't bother.  Select the compiler option for "Smart
	Callbacks" and forget it.  You don't need entries in the .DEF file
	and you don't need to mark the functions as _export this way.

>This is really driving me up a wall.  Oh, I just compiled FFIND.PRJ and
>found that it dies under WIN /R....haven't tested otherwise though.

Borland C++ does not make apps compatible with real mode Windows.  I thought
that was quite clear in the documentation.

John Munsch