Niko what would be cool is that you design a new interface so that we can see how it feels and we integrate it.
rename is for simple and fast stuff. Migrating is for used software. :) On Nov 4, 2009, at 10:20 AM, Niko Schwarz wrote: > Every project needs to have sacred cows that may not be tipped :D. > > Well, alright, in case that we can't agree on renaming, how about my > original proposal, which left everything the way it was and only added > the class-side compile:onClass: method to Compiler? Possibly sided by > compile:onClass:ifFail: > > Cheers, > > Niko > > On Tue, Nov 3, 2009 at 10:23 PM, Lukas Renggli <[email protected]> > wrote: >>> Well, I can rename the compile: method and post to PharoInbox, if >>> anyone is interested. >> >> Also I agree that it is confusing, but there are tons of projects >> that >> depend on this function. #compile: and #compile:classified: are about >> the only two compiler related methods that are available cross >> platform. If you rename them you will break any code that compiles >> something, including the Refactoring Browser, SmaCC, OmniBrowser, >> Seaside (for the file libraries), etc. >> >> 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
