From: Jurko Gospodnetic' (jurko.gospodnetic_at_[hidden])
Date: 2007-10-08 18:54:38
> OTOH, keeping everything as just globals is slightly easier to code.
> Anybody can comment, better with practical concerns, which approach
> is better?
Not a Python expert or all that versed in Boost Build internals but
when I have such a dilemma in our programs we usually go with a single
globally accessible context singleton holding all such data. Its allows
the same simple/fast coding style as raw global data but also allows
relatively low cost transition to multiple contexts if and when that
We recently had to transform a single-user application to a
multiple-user server application. User context was extracted in such a
way and the transformation was incredibly smooth.
I'd recommend going with multiple context support at once only if you
have an actual use case already planned for the initial release.
Just my 2 cents worth... hope it helps...
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk