Re: [jamboost] template main-target documentation

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-03-07 21:03:13

----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>

> >I agree with you, and wouldn't like to limit the scope. Just
> >experimenting with different names, how does "base" sound to you?
>
> How about "prototype", as in one is defining a prototype of a target.
Using
> template reminds too much of the C++ template, and base is too common
of a
> name, it's even in the example :-)

Let's see:

exe my-test : <base>boost-test ... ;
extension comprehensive : <base>boost-python comprehensive.cpp ;

vs.

exe my-test : <prototype>boost-test ... ;
extension comprehensive : <prototype>boost-python comprehensive.cpp
;

So, I like the name template or prototype (slight preference for
prototype) when declaring one of these things, but when using it, I
rather like "base" because it describes the relationship to the
dependent target.

> Also as far as the previous discussion about having "global" or C++
style
> scope names... I think I'm OK with not having that and leaving it as
is. When
> we get the additional project support in V2 we should be able to then
refer to
> project rooted names so this is not really a concern.

I think that eventually C++ scope will be important. Just compare the
above with what you get otherwise:

exe my-test : <base>../../boost-test ... ;
extension comprehensive : <base>../../libs/python/build/boost-python
comprehensive.cpp ;

-Dave