[Bf-committers] problems with C++
jesterking at letwory.net
Tue Oct 4 08:47:27 CEST 2005
It's the library issue I was thinking of :) I looked at the example
another time - it does compile after all (but man, that's a heap of
warnings), so my bad!
> Hmm... it's a bit odd that it should work for one case but not two. I'm
> running Linux only though, so I can't test with anything more than gcc.
> I agree that having to declare every template usage does make things
> more difficult, but it doesn't completely defeat the purpose of
> templates; afterall, you don't have to re-specify the *entire* class,
> under some different name, for each combination of types, you just add a
> single line to achieve that effect. In most scenarios I've seen, a
> final source tree will only use very limited number of combinations of
> template parameters. If the number is excessive, you could even
> generate them using a script to produce all the required combinations.
> Obviously, it's far far less useful for a library of templated classes!
> Let's see whether the C++ experts have any suggestions. This was only
> one idea; something I've used in the past (on my own internal, gcc-only
> projects) to avoid having enormous header files included with each *.cpp
> Bf-committers mailing list
> Bf-committers at projects.blender.org
More information about the Bf-committers