Stéphane Ducasse wrote: >> > > I should really use Sake to understand it further. > Now what is clear to me is that I like the idea. We need something to > write build script. > > Now for the classTasks, I'm a bit worried that we can do this kind of > actions > becuse it means that depending on the task used to create a given > distribution > we can have a side effect method removed, added, class added .... > I dont understand your objection...
action blocks can contain any code. Class tasks are simply short hand for (Smalltalk at: #Cup ifAbsent: [ nil ]) ifNotNil: [ :c | c ... do something ] and all that jazz. Having a task requiring a class to exist, is no different to having a task requiring a file or directory to exist in a non image based environment. regards Keith _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
