From:	mvoss AT kuttig DOT com
Subject:	RE: Re: Linker: Bug or Feature?
19 Nov 1998 17:04:38 -0800 :
Message-ID:	<C12566C1.0034B195.00.cygnus.gnu-win32@notes.kuttig.com>
Mime-Version:	1.0
To:	tjump AT cais DOT com
Cc:	gnu-win32 AT cygnus DOT com

Hi! you wrote:

>>

>>Explanation
>>In asm or .c file if you defined a function whose protype is:
>>   int foofunc(int x);
>>This will create a function with linkage signature "_foofunc"
>>If you create the same function prototype but compile it with a C++
compiler,
>>it will create a function with a linkage signature similar to
>>"?foofunc@@YAHH AT Z" - this is called name mangling and is done partially
to
>>ensure that the correction function get's called for the correct
parameter
>>types since you can overload different functions with the same name.
Okay, that makes this "bug" a "feature". I now understand what the name
mangling is for :-)
But then: How can I overload external assembler functions? Since the name
mangling differs from compiler to compiler, what can I do to maintain
portability?

>>To make it possible to call the c/asm function from c++, you must declare
the
>>prototype like this for C++:
>>   extern "C" int foofunc(int x);

THANK YOU!
This helps....

One more question: Given an "int i", I always thought "i++" or "i--" was
c++ only, but "i=i+1" or "i=i-1" was c and c++. Since I always use "i++" in
my loops, doesn't this make my code c++ automatically? So what does the
c-compiler do with this?

(don't beat me if I got something terribly wrong here........I read that in
a C++ book five years ago.)



Anyway, thaks for the numerous replies - they really helped.


Thakfully,
 Moritz


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -