Re: [jamboost] Boost.Build V2, load behaviour part 2.

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-03-31 12:03:52

----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>
To: <jamboost_at_[hidden]>
Sent: Sunday, March 31, 2002 11:52 AM
Subject: Re: [jamboost] Boost.Build V2, load behaviour part 2.

> On 2002-03-31 at 08:46 AM, david.abrahams_at_[hidden] (David Abrahams)
wrote:
>
> >----- Original Message -----
> >From: "Rene Rivera" <grafik666_at_[hidden]>
> >
> >
> >> On 2002-03-30 at 09:21 PM, david.abrahams_at_[hidden] (David Abrahams)
> >wrote:
> >>
> >> >Question: what is a "module-tag" supposed to be?
> >>
> >> It's the tag to use to identify the module as being loaded or not.
> >Maybe
> >> "load-tag" is better? Any suggestions welcome :-)
> >
> >Why can't it always be derived from the module-name? Every module
must
> >have a unique identifier anyway. I'm sure you have a reason, but
please
> >spell it out...
>
> To be specific, I need to call load to load the Jamfiles, but they
need to be
> in the module of the project-root...

Do they? What are the negative implications of doing otherwise? One
thing I see, which I rather like, is that even in large projects each
subproject would have its own variable namespace.

> modules.load <project-root-module> : <Jamfile> : <some-jamfile-dir> :
> <some-jamfile-dir>/<Jamfile> ;
>
> So it will include the Jamfile inside the <project-root-module> but
use the
> <some-jamfile-dir>/<Jamfile> to decide wether it's been loaded already
or not.
> Maybe a name closer to C++ might help, how about "module-key"?

Naw, tag is fine, but it has nothing to do with the module. It is a file
identifier. Why don't you just derive that directly from the file (with
perhaps a little path normalization/simplification?)

> >> Question, is there a way to get the argument template of a rule?
...So
> >I could
> >> print it as part of a rule's doc.
> >
> >HDDRULE, HDRSCAN, baby. I'm telling you, doing doc dumps as build
> >actions has lots of advantages. You could even extract doc from
comment
> >blocks, so there's no issue with interpretation of $() or
space/newline
> >(though I guess strings work pretty well in Jam).
>
> :-) ... but you can't handle --help* with HD* ;-\

Why not?
You just need to write an action which dumps the help, right?