Subj : Forwarder DLLs
To   : Andrew Belov
From : David Noon
Date : Tue Mar 20 2001 04:05 pm

Hi Andrew,

Replying to a message of Andrew Belov to David Noon:

[snip]
 AB> That is the problem I'll have to investigate. Do I need to supply code
 AB> for all and any ordinal being forwarded, or there is an easier
 AB> approach (e.g. by duplicating the name both in IMPORTS section and in
 AB> EXPORTS)?

I just tried it out using VAC++ 3.0 and it works. ILINK.EXE gives a warning 
about creating a forwarder when it links the "middle" DLL, but everything 
works. The .EXE I wrote called 2 routines, ostensibly from the same DLL, but 
one was actually in another DLL; both DLL's were loaded correctly and both 
routines were called correctly.

So, just import in one part of your .DEF file and export in another. Only 
supply code for the specific routines you want to hack.

Regards

Dave
<Team PL/I>

--- FleetStreet 1.25.1
 * Origin: My other computer is an IBM S/390 (2:257/609.5)

.