home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.programmer.misc:4737 comp.lang.pascal:7960
- Path: sparky!uunet!usc!sdd.hp.com!sgiblab!a2i!shakala!donh
- From: donh@shakala.com (Don Hackler)
- Newsgroups: comp.os.ms-windows.programmer.misc,comp.lang.pascal
- Subject: Re: DLL Procedure/Function Calls ???
- Message-ID: <VyT2wB4w165w@shakala.com>
- Date: Fri, 08 Jan 93 00:12:06 PST
- References: <dmurdoch.381.726439606@mast.queensu.ca>
- Organization: Shakala BBS (ClanZen Radio Network) Sunnyvale, CA 408-734-2289
- Lines: 30
-
- dmurdoch@mast.queensu.ca (Duncan Murdoch) writes:
-
- > In article <1993Jan7.184304.3453@scf.loral.com> andres@scf16.scf.loral.com (J
- >
- > >Target Compiler: BP7
- > >Goal: Generate Windows Program
- >
- > >Problem/puzzle:
- >
- > > Windows, likewise vendors and programmers, often supply .DLLs
- > >for use by others. Is there a convient way to find out what the calling
- > >convention is to utilize the procedures/functions contained ? Is there
- > >a way to get like a "directory" listing of available calls ?
- >
- > There's a list of external entry points in the .DLL, but no information
- > there about calling conventions. You could use a disassembler to try to
- > figure it out (e.g. my Dumpprog, on garbo.uwasa.fi as
- > /pc/turbopas/dmpprg20.zip) by looking at the code following the entry points,
- > but it's not easy.
- >
-
- Or get Undocumented Windows by Andrew Shulman... which
- includes the utilities to dump the DLL entry points, and lots
- of other good stuff...
-
- - don
-
- ------------------------------------------------------------------
- Don Hackler - donh@shakala.com
- Shakala BBS (ClanZen Radio Network) Sunnyvale, CA 408-734-2289
-