i would like to suggest that JAMES adopts a slightly different approach to the development of extra and alternative functions. ATM we use branches for experimentation but i think that these are several disadvantages in this:
* collaboration is more difficult * hard to shared between branches * more difficult to compare and contrast different approaches to similar problems * hard to take advantages of improvement in code made on the trunk with the new modular system i think that it should be possible to develop addition and alternative functions in trunk by using experimental modules. so, i would like to propose we allow experimental modules in trunk. these will be prefixed 'experimental' and contain either alternative implementations or new functions which are not yet mature enough to be a full part of JAMES. these modules would not be included by default in JAMES but would included as part of the unified build and could be added in by altering the configuration. opinions? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
