Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!caen!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uunet!ns-mx!ccad.uiowa.edu!cadsi
From: cadsi@ccad.uiowa.edu (CADSI)
Newsgroups: comp.windows.ms.programmer
Subject: Re: DLL's, _export and C++ classes in BC++
Message-ID: <1991May17.023332.8673@ccad.uiowa.edu>
Date: 17 May 91 02:33:32 GMT
References: <42360@cup.portal.com>
Distribution: usa
Organization: CAD-Research, U. of Iowa, Iowa City, Iowa
Lines: 34

From article <42360@cup.portal.com>, by David_Dave_Tamashiro@cup.portal.com:
> This might be a dumb answer, but did you look at the dlldemo.exe that
> is included with BC++?   Maybe that will have your answer.
> 
> 
> Dave

Yes I had.  BUT, I think I solved it.  I forgot to put the _export
keyword on the actual methods in the source files.  I did put the _export
on the class for the DLL and huge for outsiders.  BUT, like a dope, I
neglected the actual method:

	_HashINT32 HashTable::lookup(...)

is really supposed to be:

	_HashINT32 _export HashTable::lookup(...)

Now, Mr. Borland out there, the linker was not exactly helpfull since it
only reported that

	unsigned long HashTable::lookup(unsigned long)

was undefined (I have _HashINT32 typedefs), not

	unsigned long _export HashTable::lookup(unsigned long)

I know how it is though, but think on it.

|----------------------------------------------------------------------------|
|Tom Hite					|  The views expressed by me |
|Manager, Product development			|  are mine, not necessarily |
|CADSI (Computer Aided Design Software Inc.	|  the views of CADSI.       |
|----------------------------------------------------------------------------|