Re: Calling external procedure

> I'm curious, what is the intended interface language to this
> interface?

Straight C, if I understand the question.

> It is possible the procedure name is a variation of the published
> name. For example, a procedure with the documented name of FooBar may
> require FooBarA for an ASCII interface or FooBarW for a Unicode
> interface. I work with a DLL that had the stack frame size as part of
> the name (FooBar with 3 parameters was FooBar12).

There seems to be only one exported function, but that function provides the
addresses for about 20 more with 0 to 3 parameters.
Here's the dumpbin /EXPORTS aardvark.dll

File Type: DLL

  Section contains the following exports for aardvark.dll

           0 characteristics
    3EEE0F78 time date stamp Mon Jun 16 11:42:00 2003
        0.00 version
           1 ordinal base
           1 number of functions
           1 number of names

    ordinal hint RVA name

          1 0 000014B0 aa_load_function

  Summary

        1000 .bss
        1000 .data
        1000 .edata
        1000 .idata
        1000 .rdata
        1000 .reloc
        6000 .text

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
For list command help, send subject "help" to sftalk-request_at_forth.com
Message archives are located at http://www.forth.com/archive/sftalk
----------------------------------------------------------------------
This list is a forum for SwiftForth users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Mon Jul 21 2003 - 09:41:28 PDT