It's a matter of priorities. We decided for instance that license cleaning, closures, and making all tests green is more important than ANSI compliance. Of course, we could add stuff like ANSI to the list, but then we will never deliver, not event a first version, because there is always something important to be done. Its not a question of will, but of resources. If people feel that Pharo cannot be used because its not compliant they are welcome to provide improvements. If people feel that Pharo cannot be used because its not compliant and they are not able to provide improvements then they can simply choose something else.
Adrian On May 28, 2009, at 22:29 , Lukas Renggli wrote: >> Full compliance, on the other hand, is not a primary goal. > > ANSI Smalltalk is nominal. Too minimal for many tasks, and still > people build their frameworks on these foundations to keep their code > portable across platforms. If you undermine the Smalltalk standard, > Pharo simply can't be the choice for open-source development anymore. > Full ANSI compliance must a primary goal. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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
