Development plan

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-01-23 11:13:39

Now that we have the major "how will it work?" questions answered, it's time
to get started on the programming. First, I'd like to have a short
discussion of what the jobs are. Here are some of the jobs I can see; I hope
y'all can help me fill in the detail so we can start dividing up the work.

Core Jam: Steal PWD from Matt Armstrong
Core Jam: Add ARGV rule

Implement Initialization/Configuration

Abstract targets:
Registration (name, sources, type, requirements, etc.)
Retrieving a list after Jamfile is read
(sub)projects as abstract targets
retrieving based on path/@projectid notation

Features and Properties (some of this is done in features.jam):
Expansion
Matching utilities

Target types (implemented atop features/properties):
Declaration
Implement refinement hierarchy and expansion

Generators
Definition of interface
Declaration/registration
High-level generator classes for common cases
Relevance filtering
Subvariant Identification

Virtual Targets
Representation of dependencies
Cache of already-generated virtual targets

Source->Target Expansion Process
Finding generator set
Build Property Expansion
Virtual Target Generation
Actual Target Generation

Implementation of a few toolsets in the new framework

Test cases

???

===================================================
David Abrahams, C++ library designer for hire
resume: http://users.rcn.com/abrahams/resume.html

C++ Booster (http://www.boost.org)
email: david.abrahams_at_[hidden]
===================================================