delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/10/01/19:15:24

From: "Wim Cools" <w DOT cools AT chello DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: Problem with .O file
Lines: 20
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: <zhPB5.27902$Sb1.503963@nlnews00.chello.com>
Date: Sun, 01 Oct 2000 22:55:27 GMT
NNTP-Posting-Host: 212.83.89.103
X-Complaints-To: abuse AT chello DOT nl
X-Trace: nlnews00.chello.com 970440927 212.83.89.103 (Sun, 01 Oct 2000 21:55:27 GMT)
NNTP-Posting-Date: Sun, 01 Oct 2000 21:55:27 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

When I compile a program with a function like this:

void blah()
{
    DoSomething();
    printf("Done.\n");
}

and compile it (as a C++ file) and I take a look a the .O file (blah.o in
this example) I see
the keyword _DoSomething__Fv instead of _DoSomething when I compile it in
C-mode.
Because I'm using a Dynamic Link library and I have to create a file with
export keywords I just want to write DoSomething and not that
DoSomething__Fv. Does anybody know what this "__Fv" means and how I can
prevent the compiler from adding __Fv to each function-keyword.

Thanx.


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019