home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!math.fu-berlin.de!Sirius.dfn.de!Urmel.Informatik.RWTH-Aachen.DE!dfv.rwth-aachen.de!sungate.fido.de!p1.hippo.fido.de!softstream.fido.de!Thomas_Hornschuh
- Date: Wed, 18 Nov 92 03:45:12 +0100
- From: Thomas_Hornschuh@softstream.fido.de (Thomas Hornschuh)
- Subject: Re: BC++ far* default in medi
- Message-ID: <1b9d9f42@p1.f36.n245.z2.fidonet.org>
- References: <18657@ksr.com>
- Newsgroups: comp.os.ms-windows.programmer.tools
- X-Comment-To: kenyee@sneakers (Ken Yee)
- Organization: SoftStream Development, Dortmund, Germany
- Lines: 13
-
- KY> possible to do a FAR PASCAL varargs procedure exportable from a DLL?
- KY> when calling this procedure from inside the library, the parameters
- KY> come in as zeros.
- KY> I hacked it by making the exports non-varargs, but it's ugly.
-
- Pascal procedure never can have vargargs, because with the pascal calling
- convention the called procedure must clean up the stack. But only the caller
- knows how much data was passed...
-
- If you want to export a function with variable number of arguments simply
- remove the PASCAL keyword. The function will now use C callling conventions.
- PASCAL is not a must for a exported funtion, only a convention.
-
-