Thread View: comp.windows.ms.programmer
1 messages
1 total messages
Started by Thomas Hornschuh
Mon, 13 Apr 1992 19:38
Re: Function export problem when porting MSC code to BC 2.0
Author: Thomas Hornschuh
Date: Mon, 13 Apr 1992 19:38
Date: Mon, 13 Apr 1992 19:38
18 lines
1372 bytes
1372 bytes
JT> JT> Attempt to export non-public symbol XXXXX JT> JT> where XXXXX is the name of the dialog function. The dialogs are called JT> through MakeProcInstance(XXXXX, hInst) which are all listed under JT> EXPORTS in .def file. If your are using the C++ parser you must declare all exportable functions with extern "C" FAR PASCAL ...... because PASCAL alone will not switch off the C++ name mangling. But if you only export callbacks in an exe there are simpler methods: 1. use the keyword _export in together with FAR PASCAL. BC will export the function automaticly, you need not list it in the EXPORT section of a DEF file. 2. If you do not compile a DLL, you can switch on "smart callbacks". Then you don't need exports or a call to MakrProcInstance for your callback functions.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads