Article View: comp.windows.ms.programmer
Article #415Re: Function export problem when porting MSC code to BC 2.0
From: 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.
Technical Details
Message-ID:
<15e995ef@p1.f36.n245.z2.fidonet.org>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!mips!darwin.sura.net!Sirius.dfn.de!urmel!slcdec!sungate.fido.de!p1.hippo.fido.de!softstream.fido.de!Thomas_HornschuhShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!mips!darwin.sura.net!Sirius.dfn.de!urmel!slcdec!sungate.fido.de!p1.hippo.fido.de!softstream.fido.de!Thomas_Hornschuh Date: Mon, 13 Apr 92 21:38:20 +0200 From: Thomas_Hornschuh@softstream.fido.de (Thomas Hornschuh) Subject: Re: Function export problem when porting MSC code to BC 2.0 Message-ID: <15e995ef@p1.f36.n245.z2.fidonet.org> Newsgroups: comp.windows.ms.programmer X-Comment-To: Jin_Tonic_Li@f1.n6000.z2.fidonet.org (Jin Tonic Li) Organization: SoftStream Development, Dortmund, FRG Lines: 23