Re: Help a newbie understand how to create a "native library" for any new language

haberg@math.su.se (Hans Aberg)
15 May 2005 15:44:31 -0400

          From comp.compilers
Related articles
Help a newbie understand how to create a "native library" for any new rdc02271@yahoo.com (rdc02271) (2005-05-14)
Re: Help a newbie understand how to create a "native library" for any haberg@math.su.se (2005-05-14)
Re: Help a newbie understand how to create a "native library" for any skandgoe@gwdg.de (Skandinavisches Seminar) (2005-05-14)
Re: Help a newbie understand how to create a "native library" for any haberg@math.su.se (2005-05-15)
| List of all articles for this month |
From: haberg@math.su.se (Hans Aberg)
Newsgroups: comp.compilers
Date: 15 May 2005 15:44:31 -0400
Organization: Mathematics
References: 05-05-093 05-05-107
Keywords: design
Posted-Date: 15 May 2005 15:44:31 EDT

"Skandinavisches Seminar" <skandgoe@gwdg.de> wrote:


> Generally speaking, a library for C will be written in C, a library
> for C++ in C++, etc.


Even though this is true on the source code level, it seems that on
the object code level, one way to do it is to mangle the code into a
C-library. For example, when doing this, the C++ directive 'extern "C"
....' becomes a directive 'do not C++ mangle ..., but use C
conventions directly'.


--
    Hans Aberg

Post a followup to this message

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