Le 05/05/2010 15:24, Torsten Bergmann a écrit :
P.S: I'm still in favour of well structured books in separate packages than mixed code/docu in one package since you may wish to unload docu for deployment/runtime scenarios.
Hi Torsten, all Yes, we had exactly the same discussion (one year ago? I can't believe it) about the settings package. An advantage of the builder approach is that one can simply choose: It is possible to let documentation methods (#helpOn: aBuilder ...) and code mixed in a single package without introducing any dependency or choose to have two packages, one for the documentation and the second for the code. Cheers Alain
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project