[C++-sig] high level overview of boost.python implementation

[David Abrahams]

----- Original Message -----
From: "Joel de Guzman" <djowel at gmx.co.uk>

> Great!
>
> Do we have a layer/module diagram(map) of the library?

Nope.

> This is a good
> starting
> point to get the *big picture*.

Agreed.

> To make my point clear, for instance
> here's Phoenix's
> layer/module diagram:
>
> ::Organization
>
>     The framework is organized in five (5) layers.
>
>                      +-----------+
>                      |  binders  |
>                      +-----------+-----------+------------+
>                      | functions | operators | statements |
>         +------------+-----------+-----------+------------+
>         | primitives |             composite              |
>         +------------+------------------------------------+
>         |                     actor                       |
>         +-------------------------------------------------+
>         |                     tuples                      |
>         +-------------------------------------------------+

I'm not sure the library lends itself to this sort of decomposition -- the
dependency graph may be too complicated to lay out in 2d without some arc
crossings -- but I could be wrong.

Let me know how I can help.

> Then, we can proceed bottom-up.

Sounds good to me.

-Dave