Linking and Libraries

I have two questions :D

First off,

When you include a header file in your program, does the compiler then link the program to the library that it intails? Or are the libraries always linked? I´d assume that they´re only linked when the header is included, but how does that work?

Secondly,

Recently, I wrote a program as a test that was composed to two cpp files. I then wrote two functions that were *exactly* the same and put on into each file. I then prototyped the one function in the first file (the on with main() in it) and made a call to it in main(). I assumed that I would get some sort of error, ambiguity or such, but no such error occurred, and the program simply called the function in the first file. Why?


thanks very very much for the help!

1. The header files are linked to the libraries and at compile time those libraries are then included in your program.

2. Well, I do recieve an error as expected from the linker informing me that the function was already defined in another file.
I am using VS.NET 2002. What are you using?

>I´d assume that they´re only linked when the header is included
Or they're linked if a name from the header is actually used. That way you don't pay for what you don't use. It really depends on the linker involved, so your question is implementation dependent. However, to save yourself unnecessary grief, you should assume that each header forces the linker to load the object file for that header. If the header isn't included then the object file isn't loaded, even if you declare the name yourself.

>Why?
I get a linker error complaining about multiple definitions. Post the code you've been using as well as your compiler and the switches you're using to invoke it (if applicable).

Quote:

---

does the compiler then link the program to the library that it intails?

---

No, that is the linkers job - not the compilers.

bithub: right ;)

im not near my compiler right now, but it is visual studio .net 2003

The code was something like this:

first file

Code:

---


void test();

int main()
{
    test();
}

void test()
{
    std::cout << "test";
}

---

second file

Code:

---

void test()
{
    std::cout << "test";
}

---

mayble it only links the files if it sees a function call to an alien function? and it just assumes theres only one test since its only prototyped once?

Did you compile and link, or just compile? After including iostream in both files, the project will compile cleanly, but as soon as it tries to link you'll get an error complaining about test being defined more than once.

Considering that both functions give the exact same output how can you tell which is being called?

Of course if you want multiple definations you can change the linkage :)
bt9.cpp

Code:

---

#include <iostream>
void test();
void foo();

int main()
{
  test();
  foo();
}

void test()
{
  std::cout<<"Test in bt9"<<std::endl;
}

---

bt10.cpp

Code:

---

#include <iostream>
static void test();

void foo()
{
  test();
}

static void test()
{
  std::cout<<"Test in bt10"<<std::endl;
}

---

:)

>static void test();
This is a deprecated feature. To give a global name internal linkage, nest it in an unnamed namespace:

Code:

---

namespace {
  void test();
}

---

>static void test()
>{
Just FYI, only the first occurance of static is required to give a function internal linkage. So this is perfectly acceptable:

Code:

---

#include <iostream>
static void test();

void foo()
{
  test();
}

void test()
{
  std::cout<<"Test in bt10"<<std::endl;
}

---

:)

yeah, i compiled and linked... weird...
are you using visual studio .net 2003 prelude?

>are you using visual studio .net 2003 prelude?
That's one of the compilers I use, yes.

Thanks Prelude. I do sooo much internal linkage that I forgot about those rules :)

edit: Hey Prelude I'm having trouble finding where in the standard it says that static is deprecated for linkage. Mind pointint me to the right section? I'm still learning where everything is at :)

>I do sooo much internal linkage that I forgot about those rules
Internal linkage is your happy fuzzy security blanket. By forcing strict linkage, you save yourself headaches when working on large projects. :)

prelude: the program i posted above gives a linking error when you build in vc++ .net 2003? because if it does i must have just been mistaken in thinking it worked.

>the program i posted above gives a linking error when you build in vc++ .net 2003?

Quote:

---

------ Rebuild All started: Project: Cpp, Configuration: Debug Win32 ------

Deleting intermediate files and output files for project 'Cpp', configuration 'Debug|Win32'.
Compiling...
Cpp2.cpp
Cpp.cpp
Generating Code...
Linking...
Cpp2.obj : error LNK2005: "void __cdecl test(void)" (?test@@YAXXZ) already defined in Cpp.obj
C:\Documents and Settings\CCoder\My Documents\Visual Studio Projects\Cpp\Debug\Cpp.exe : fatal error LNK1169: one or more multiply defined symbols found

Build log was saved at "file://c:\Documents and Settings\CCoder\My Documents\Visual Studio Projects\Cpp\Debug\BuildLog.htm"
Cpp - 2 error(s), 0 warning(s)


---------------------- Done ----------------------

Rebuild All: 0 succeeded, 1 failed, 0 skipped

---

alright, thanks.