Date:	Mon, 2 Oct 2000 12:01:10 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Wim Cools <w DOT cools AT chello DOT nl>
cc:	djgpp AT delorie DOT com
Subject:	Re: Problem with .O file
In-Reply-To:	<z5WB5.30215$Sb1.514064@nlnews00.chello.com>
Message-ID:	<Pine.SUN.3.91.1001002115923.29084A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 2 Oct 2000, Wim Cools wrote:

> > >Does anybody knowwhat this "__Fv" means
> >
> > It's C++ name mangling.
> >
> > >and how I can prevent the compiler from adding __Fv
> >
> > extern "C" void blah()
> > {
> >   ...
> > }
> >
> > The `extern "C"' will compile the function using C language calling
> > conventions.
>
> Thanx, but the "__Fv" addition it still there in the .O file...
> Is there maybe another way to fix this?

Using ``extern "C"'' is the _only_ way to fix this, and it always works.  
If it didn't work for you, you must have done something wrong.

The best way of getting a useful response is to post your code (after 
adding ``extern "C"''), and then describe exactly what seems to be wrong 
with the object file.

- Raw text -