🚀 go-pugleaf

Sorry Rohan,

In the name of sowing snow on confusion, I have to disagree. 
Or maybe I misunderstood the original question.

What do you say to this:
 [1] g++ has to see both template interface (*.hh) and implementation (*.C),
     by magic (`-frepo') or in front of her nose, to instantiate.
 [2] this doesn't mean that *.C has to be put in *.hh (dependency nightmare)

ag> From: rjl@f111.iassf.easams.com.au (Rohan LENARD) writes:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ag> In article <471ltm$vtd@penny.tagsys.com>,
ag> Andrew Gideon <andrew@tagsys.com> wrote:
ag> :In article AA05482@brie, albert@inrs-telecom.uquebec.ca (Albert Golembiowski) writes:
ag> :>Of course it's possible with g++-2.7.0 to include only interface headers,
ag> :>templates or not. To carry along template implementations, as suggested
ag> :>below, is to create dependency nightmare, i.e. any change
ag> :>in `mytemplates.cc' might put you through the amazing experience of watching
ag> :>the whole world recompile!
ag> :>
ag> :>Not to mention that doing this with any sizable project will make your
ag> :>compiler eat all the available memory, then proceed to your pets, then ...:-)
ag> :>
ag> :
ag> :Well, I don't want to lose my cats to a greedy compiler.
ag> :
ag> :I was not aware that I no longer needed to include the source
ag> :file (from the template header file).   I'm including the sources now, 
ag> :and things seem to work.
ag> 
ag> You can only do this if -
ag> 
ag> 1.	You use -frepo
ag> 2.	You need to compile at least 1 version of the source (so g++ knows
ag> 	where to find the class definition).
ag> 

-- 
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Albert Golembiowski      albert@inrs-telecom.uquebec.ca         (514) 762-8655
INRS Telecommunications, 16 Place du Commerce, Verdun, Quebec, Canada, H3E 1H6
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""