As I don't really know where to put, its not really EE related, but is based on something I wondered when browsing the EE headers:

I always wonder how Grzegorz managed to split up header and source of the template classes.

I searched the web and found nothing that answers the question (or at least I'm searching for the wrong thing). I always thought definition and implementation needs to be within one class, but it looks like he managed to split into header and sources. While the header are published for us to be used.

Whenever I try to create a template class with just a constuctor, I'll get a LNK2019 when moving the constructors source from header to source file.

Template-Header:

Template-Source:
Note:
The class is part of a static library being linked by another project.

And in that another project I'll get a LNK2019 whenever I want to use that class within my code:
TClass<int> _intInstance;

Maybe anybody can give me a hint how to solve this problem, like he did with Esenthel...still wondering how

If you ask where this occured: "Mem Continiuous.h" for example, in fact all memory containers are build like that in EE.

Not sure how EE does it (and I can't look at it right now), but one way to do it would be to have a precompiled version of said header with the implementation, and a second one for our viewing.

So when he includes the file, the preprocessor will actually get the precomp, but if you search for the filename, you'll get the reduced version.

Another thing would be to have the declaration and definition in different header files (whatever the extension), and then take care to include them both somehow in correct order. The second could be hidden in some ways, or precompiled (if the compiler supports more than one precomp / precomps after regular headers - which VS doesn't).

Or, if it is just an Esenthel Script thing, he could have just removed the limitation.

Other than that.. I've no idea.

http://www.codeproject.com/Articles/4857...le-and-imp

Function body for templates must be included in the headers as well.
Many EE template func bodies are just separated and stored in another header file Misc/Templates.h

Edit: OH, never have seen that file before, thank you very much! ^^



Thanks Zervox, that are some really nice approaches, but id doesn't make it clear for 100% in case of EE:

- Method 1: Esenthel don't know about custom structs defined by the client and used by a mem container
- Method 2: I don't see any implementation include in any of the Memory Container examples
- Method 3: There is no implementation include in the "Installation"-Headers files

Is there anything else possible, as I don't really see it right now :/

In Code Editor you can just middle mouse click a function and it will jump between func definition/declaration.