Re: multi calling convention libraries

Why bother? All it takes is a slight change to a calling convention
and your libraries are all obsolete, and what's worse, probably
pathological. I think it would also violate the spirit of the ANSI C++
standard on mangling.


Presuming here you're talking about C++, it's possible to design
libraries carefully such that they can be used in a binary-compatible
way between different compilers (look at COM or CORBA for examples).


The key is not to export mangled names, but to export extern "C"
functions that return pointers to objects. These objects are opaque to
the library, but the interface to the object is defined in an pure
abstract base class.


What is the higher-level problem you are trying to solve?


alan


Wolfgang.Hospital@Materna.DE wrote:
>
> I have been toying around with the idea of including entry points
> (symbols and code) for several calling conventions in one library
------------------------------------------------------------------------
    Alan Donovan adonovan@imerge.co.uk http://www.imerge.co.uk
    Imerge Ltd. +44 1223 875265

Return to the comp.compilers page.
Search the comp.compilers archives again.