From: "Wim Cools" Newsgroups: comp.os.msdos.djgpp References: <15hfts4plrcsoapu9rfd8bs5p448dv05fc AT 4ax DOT com> Subject: Re: Problem with .O file Lines: 27 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Message-ID: Date: Mon, 02 Oct 2000 06:40:31 GMT NNTP-Posting-Host: 212.83.89.103 X-Complaints-To: abuse AT chello DOT nl X-Trace: nlnews00.chello.com 970468831 212.83.89.103 (Mon, 02 Oct 2000 05:40:31 GMT) NNTP-Posting-Date: Mon, 02 Oct 2000 05:40:31 GMT Organization: chello broadband To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > > >I see the keyword _DoSomething__Fv instead of _DoSomething when I > >compile it in C-mode. Because I'm using a Dynamic Link library > > DJGPP doesn't support DLLs. Are you creating a static library (*.a)? > No dynamic linking packages like DLM and DLX > >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?