Re: [jamboost] Re: Type registration and main target rules

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-10 03:29:18

On Friday 10 December 2004 05:43, David Abrahams wrote:
> Vladimir Prus wrote:
> > David Abrahams wrote:
> >>> Dave, this means you don't need to tweak boostbook.jam to make your
> >>> docutils module work, just make sure boostbook is imported (so that
> >>> HTML type is defined).
> >>
> >> Right. Now shouldn't we move the declaration of HTML somewhere else?
> >> BoostBook isn't the only client for it.
> >
> > Probably. The only suitable module seems to be builtin.jam. (unless we
> > want a separate module just for HTML type). Feel free to move the type
> > declaration.
>
> I just committed a change that factors the declaration out of
> boostbook.jam and simultaneously gives us a system for dropping in new
> types without intruding on builtin.jam. 

That's very good. The size of builtin.jam is already alarming, so splitting it 
in parts is nice.

> I didn't want to cause too much 
> churn in the codebase, so I haven't done it, but I think most of what's
> in builtin.jam could be broken out into types/*.jam. For example, the C
> and H types could go into types/cpp.jam along with the c-scanner. I
> think we should discuss the specifics before doing anything drastic,
> though.

Moving C,H and c-scanner to type/cpp.jam seems pretty safe to me. There's a 
question what we do with all those 'lib-generator', 'archive-generator' and 
so on. They are more convenience for toolset modules which define 
compiler-specific generators, so moving them to type/lib.jam does not seem 
quite as good.

- Volodya