🚀 go-pugleaf

In article <48ngc6$o7c@lava.ivg.com>, berts@noord.bart.nl says...
>
>howieu@ix.netcom.com (Howard Uman ) wrote:
>
>>I've got Visual C++ going, and when I try to build a .DLL file with the
>>Medium memory model, it fails during the link because it cannot find a
>>file called mafxdwd.lib.  This file is *NOWHERE* to be found on the
>>CD-Rom.  
>
>>If I compile and link from the command line, using a different make
>>file, but the medium memory model, it works fine (I don't link in this
>>mafxdwd.lib file).  
>
>>The problem is Visual C++ automatically adds this file and oldnames.lib
>>to our project.  We really don't need either, but oldnames doesn't blow
>>us up.  
>
>>Thanks.  Post response here and/or (preferrably, to ensure I get the
>>response) to howieu@ix.netcom.com.
>
>>     Thanks, Howie
>
>There's a good reason for the absence of the medium model library. A
>DLL should *always* be compiled in the large memory model.

Why? Seems to me that it's perfectly reasonable to want to use near pointers 
internally, and only use far pointers in the interface. One way to do this is 
to build in medium model and qualify pointers in exported functions with __far.
	-- Pete