Yes. The key problem with lot of packages is that they can rot and be forgotten. I think that at one point we should arrive to a system where lot of code is in package but we work on a system where they are automatically/ easily loadable.
Stef On May 28, 2009, at 10:02 PM, Adrian Lienhard wrote: > > On May 28, 2009, at 21:41 , John McIntosh wrote: > >> Well I think a statement of direction is required. Is *all* ANSI >> specific >> logic going to be in the base Pharo? Is base Pharo going to be >> ANSI compliant ? >> I don't think people want to load chunks of it from here and there, >> assuming >> they know they need to do that. > > I see it like this: > > - keep already existing ANSI compliant behavior > - where appropriate, fix semantics to be compliant > - where appropriate, add new ANSI behavior > > Full compliance, on the other hand, is not a primary goal. > > Cheers, > Adrian > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
