[Boost-build] Python port: globals

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-10-08 15:02:12

While working on Python port, I have a question. In Jam code,
most modules just dump all data as global objects. For Python,
some already ported code departs from that habit -- for example,
the project.jam port has class ProjectRegistry, that keeps the
list of loaded projects. There's single top-level Manager 
object that keeps all the various classes together.

This seems to be a good idea, and it makes the code more
testable, and in future, it might be possible to have some IDE
just load Python modules for Boost.Build, and then build several
Boost.Build projects by just creating different "Manager" objects.

OTOH, keeping everything as just globals is slightly easier to code.
Anybody can comment, better with practical concerns, which approach
is better?

Thanks,
Volodya