Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!fernwood!portal!cup.portal.com!David_Dave_Tamashiro
From: David_Dave_Tamashiro@cup.portal.com
Newsgroups: comp.windows.ms.programmer
Subject: Re: DLL's, _export and C++ classes in BC++
Message-ID: <42447@cup.portal.com>
Date: 18 May 91 09:27:27 GMT
References: <42360@cup.portal.com> <1991May17.023332.8673@ccad.uiowa.edu>
Distribution: usa
Organization: The Portal System (TM)
Lines: 25

Tom,
I am glad you fixed your problem.  Turns out I am working on a different
bug/feature??

It seems that when I compile C (not C++) DLL functions, I have to use
the PASCAL calling convention or else the linker will not find my DLL's
in my *.lib file.    I can get around this problem by setting the linker
to ignore upper/lower case; the code seems to work in any case.

I have a question regarding the use of the huge and _export keyword:
When I  compile C DLL's, do I still have to declare my DLL's 
as "huge" in my main application code?  I have succesfuly compiled my
main program(and linked it) using header files which alternatively
declared my DLL's as "huge" and "_export".  Is the linker going to do
something strange if it see's the "_export" function prototype in both
the DLL *.c file and the main app *.c file?

Also, does anyone know why Borland decided to use the huge keyword when
defining DLL classes?  Whats wrong with the good ole FAR keyword.  Does
their huge keyword still mean normalized far pointers (i.e. 1Mbit pointers)
or does it really mean their  pointers can access 2^32 memory locations?
  ...And... if it does, who cares??? 

Thanks,
Dave