🚀 go-pugleaf

In article <1994Mar18.094731.18956@ensmp.fr>, zhou@cri.ensmp.fr (Lei ZHOU) writes:
|> 
|> Solution for small application is to create just one file in which all the
|> instantiations are generated. This file along includes the template text files.
|> All other program files include the template header file.
|> 

I have a related problem. I am building a container class which I want
to instantiate over many diffferent element types. I write a single
(typeless) implementation and then have a class template interface which
has a bunch of inline function for doing pointer conversion so that
container class appears to be strongly typed to the user.

Now gcc compiles each instantiation of my template by creating a bunch of
local functions for each compilation unit rather than just inlining
my inline functions.

This has two obvious inefficencies: (1) I get an extra layer of function
calls between the user code and the container function. This is especially
painful where the container function was itself an inline doing a single
pointer manipulation. (2) I get code duplication in each compilation unit.

Creating a single file to hold template instantiations is a solution to (2)
but only for smallish applications. Of course the place where you really want to
use C++'s abtraction and type checking mechanisms is large apps...

Steven