Re: Progress

[2003-07-22] Daniel Wallin wrote:

>Can we try to move this along? I'm still waiting for your follow up on the
>registries thread Dave.
>
>Anyway, I have very little to do right now, so it  would be great if we
>could decide how these things should work so I can start migrating the
>luabind code to use the shared langbinding code.

Perhaps we can start on setting up cvs for the changes while Dave gets back
to the thread. [ I envy you on having free time ;-) ]

1. The branch... "langbinding" seems most logical as the branch. If there
are no objections I can add it pronto.

2. File organization. Current organization for Boost.Python is:

    boost-root/boost/python/ [converter, detail, object]
    boost-root/libs/python/ [build, doc, example, src]

I see three options for possible structure of the three parts of this. First
a total split in the parts as libraries:

    boost-root/boost/langbinding/...
    boost-root/libs/langbinding/...
    boost-root/boost/python/...
    boost-root/libs/python/...
    boost-root/boost/luabind/...
    boost-root/libs/luabind/...

Second is splitting the components but within one top-level library:

    boost-root/boost/langbinding/ [base, python, luabind]
    boost-root/libs/langbinding/src/ [base, python, luabind]

Last is keeping the langbinding base as part of the python tree:

    boost-root/boost/python/ [langbinding, ...]
    boost-root/boost/luabind/...
    boost-root/libs/python/src/ [langbinding, ...]
    boost-root/libs/luabind/...

The first one seems the clearest to me. Thoughts?


-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0