From: "Felix" <natter AT metronet DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: NASM "name mangling"
Date: Fri, 13 Nov 1998 23:58:15 +0100
Organization: -
Lines: 32
Message-ID: <72ifbf$4qm$1@news.metronet.de>
NNTP-Posting-Host: bonn2.pop.metronet.de
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

hi,
I'm using NASM 0.97 and I'm having problems with the "name mangling" feature
(to my knowledge provided for c++ overloading):
I declare a NASM function:

test.asm:
[BITS 32]
[extern _nasmtest__FPiPi]

_nasmtest_FPiPi:
...
ret
test.cpp:
extern int nasmtest(int* x, int* y);

linking this gives me a message like 'undefined reference'.
I think the syntax is right - "_nasmtest__FPi" works fine, "_nasmtest_FPii"
(nasmtest(int*, int)) also...
unfortunately the NASM docs don't have these C++ "name manglíng" things
documented.

thanks,
felix