To be more precise, I pretty sure there is only one compiler/linker that actually implements the export keyword.

And even the seperation of the .h and .cpp files does not yield what you might expect. It is not a true build once and rebuild later when there are changes. It just takes the template cpp and generates an itermediate file that it can use later when compiling other source files. And from an artical I read, it even increases build time.

I forget the name of it, but i think it is the brand that the VC6 (among others) compiler/linker was built off of.

export is very likely to be removed in future C++ standards, because it only adds complexity to the compilers without any use.

You can still write your function implementations in a .cpp or .tempate or whatever file, all you need yo do is #include them before you #endif in your header file.

quote:

---

Original post by Anonymous Poster
You can still write your function implementations in a .cpp or .tempate or whatever file, all you need yo do is #include them before you #endif in your header file.

---

Yeah, in the Almighty Boost Library, they use .ipp files for this purpose.

.ipp, .inl, .template - they all do the same thing. I just like INL because VC7 actually has an icon for it, and knows inherently not to compile it.