Hi Stef, Stéphane Ducasse wrote:
> So why do we do pharo. Really. If everything as to be compatible with > other smalltalk. Terrible. > Can't we get smarter? > Why can't we tag the methods with <notAnsi> and build a tool that > check when you > do a fill out. I do not write code to be portable to VisualWorks so? > >> I would prefer to have such extension methods separate from the core. > > Me not. Because then in a lot of places I will have to inline their > body. One of Pharo goals is to become a professional tool for serious development, specially for web apps. This implies that it should be conservative regarding introducing new and specially incompatible extensions. Because web apps are destined to be portable, so Pharo shall behave nice to other Smalltalks and avoid introducing some completely different methods in basic classes. But on the other side I agree with you, Pharo shall not be tied with that requirement too much and shall extend itself. Kind of tagging of methods as portable, pharo only etc. can therefore be a solution. Alexandre's proposal with Lint rules sounds good to me too. I would also suggest to do some promotion of good extensions to other Smalltalks as well. That way slowly Smalltalk as a whole will evolve! Pharo is right now in wonderful position to achieve such a common good for Smalltalk! Best regards Janko -- Janko Mivšek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
