🚀 go-pugleaf

Francisco M. Marzoa wrote:

Forgive me if I'm misinterpreted your post but it seems to me that
you're misunderstanding a basic principal of C/C++ development. I
apologise profusely if this is the case.

> Now, Tags is an instance of TTagList, defined on TagList.cpp. In the
> includes of ReadAll.cpp I've put:
> 
> #include "TagList.h"
> 
> But this does not make the matter, as It compiles fine, but it does
> not link later.

Why do you think there is a relationship between #include and linker
errors? It is possible for header files (and indeed any source code) to
specify files to be linked but this is unusual and not particularly
standard.

All that a header usually does is tell the compiler what the function
will look like. It's up to you to either provide the source for the
function or an OBJ or LIB file containing the compiled code for that
function.

> Method GetCount for TTagList is declared as:
> 
> protected:
>          int GetCount (void);

Again, this is just a function declaration. What the linker is
complaining about is that it can't find the function itself. You
mention 'TagList.Cpp' - I would assume this contains the code for
TTagList. Have you added this file to the project? If not then that
will be the cause of the problem.

In 'C/C++' all #include does is tell the compiler to start reading from
a different file. There is no explicit relationship between 'taglist.h'
and 'taglist.cpp'. It's only common sense, convention and modern IDEs
that lead programmers to name them that way. If 'taglist.cpp' isn't in
your project then it might as well not exist as far as the
compiler/linker are concerned.
-- 
Andrue Cope [TeamB]
[Bicester, Uk]
http://info.borland.com/newsgroups/guide.html