GC>
  > How can I successfully call functions in DLLs compiled by
  > compilers other than what I own?
GC>

  There are two issues :  name mangling and calling convention.

  Name mangling isn't really an issue, as even mangled names can be
  easily called with some nifty footwork in the .DEF file.

  If the routines use the _System calling convention then you should be
  well away.  *ALL* OS/2 compilers *must* support the _System calling
  convention (they wouldn't be able to call the system API if they
  couldn't).

  If the routines use some other non-standard calling convention, such
  as _Optlink in CSet++ or __fastcall in BC++OS2, then the DLL writer
  has locked you into one language.  If the DLLs are not compiler
  specific (C++ runtime libraries are) then this has been done for no
  good reason, and the author of the DLL deserves to be punished, for
  making the brain-dead assumption that everybody uses the same C++
  compiler that he does.

  To be fair, the vast majority of DLL writers use _System, because they
  are aware of this.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.02