Subj : Re: Using NASM and Borland C++ 5.01
To   : borland.public.cpp.borlandcpp,borland.public.tasm
From : "Ed Mulroy [TeamB]" <dont_email_me@bitbuc.ket>
Date : Wed Feb 11 2004 02:01 pm

Each symbol has a public name, the name that will be used by the linker.  C
public names are the same as in the source code except that a leading
underscore has been added.  C++ public names are formed differently.  So if
you have this function prototype:

  int MyFunc(int i);

The C public name would be _MyFunc but the C++ one might look something like
@MuFunc$qi

However if the function prototype in C++ code were this:

  extern "C"
  int MyFunc(int i);

Then the public name would be formed as if it were C langugage and might
match up with the public symbol from your assembly source file.

..  Ed

> Philip Knodl wrote in message
> news:402a707a$1@newsgroups.borland.com...
>
> Has anyone gotten NASM to work with Borland c++ 5.01?
> I've gotten NASM to generate .obj files, but when I link
> the linker complains about defined symbols.  (These are
> symbols that I define in my assembler code)
> Is there any documentation about how to use BC 5.01
> with an assmbler?

.