Xref: news2.mv.net comp.os.msdos.djgpp:3840
From: roland DOT nilsson AT communique DOT se (Roland Nilsson)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: strange function symbol names?
Date: 14 May 1996 20:10:31 GMT
Organization: -+- Private -+-
Lines: 19
Message-ID: <4napbn$3va@news.luth.se>
References: <4n89hk$dsc AT news DOT luth DOT se> <4n8g0j$1aqe AT rs18 DOT hrz DOT th-darmstadt DOT de>
NNTP-Posting-Host: x5.communique.se
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <4n8g0j$1aqe AT rs18 DOT hrz DOT th-darmstadt DOT de>, 
alexlehm AT rbg DOT informatik DOT th-darmstadt DOT de says...
>
>: I have a problem with djgpp v2 object output: it renders strange symbol
>: names for my functions. Function "foo()" renders "_foo__FPc" or
>: "_foo__FPec", not just "_foo". Why? Can this be controlled by an option?
>
>This is called C++ name mangling. The problem is that you can have the same
>function name with different parameter/return value types and the proper
>function is called depening of the types. To make the linker distinguish
>the different functions, the types are somehow encoded into the function
>names. (In a reversible manner, I think, the debugger, nm etc can correctly
>list the functions).

Ooops. I guess I knew about that - temporary brain overload. ;-)
Silly me. Thanks for pointing it out.

	Roland Nilsson