To enable us to manage Strongtalk source code in Subversion, we need to be
able to write out library subsets as a group, with each top-level entity in
a separate file. This can be done for the whole system by
#fileOutWorldToFile:, but people need to be able to work on library
subsets, so as an initial hack I would like to produce a method like
#fileOutWorldToFile: that takes a predicate that determines which classes
are included in the fileout. Something like
#fileOutMatching: pred <[Class,^Boolean]> toFile: <FilePath>
Original issue reported on code.google.com by David.Gr...@gmail.com on 22 Sep 2006 at 9:33
Original issue reported on code.google.com by
David.Gr...@gmail.com
on 22 Sep 2006 at 9:33