mmmm I found this old issue: http://code.google.com/p/pharo/issues/detail?id=1058
On Tue, Feb 9, 2010 at 2:03 PM, Mariano Martinez Peck <[email protected] > wrote: > > > 2010/2/9 Luc Fabresse <[email protected]> > > Hi all, >> >> I wonder why BlockContext>>fixTemps is still in PharoCore. >> I guess that it should be removed, isn't it? >> > > I would like to remove them. > > >> It has only one sender. >> > > Yes, in the core ;) But the problem is that Seaside (I think only 2.8.4 > as 3.0 seems to fixed that) or KomHttpServer are still using it. > > Of course, we can just remove it and assume that those external packages > should be fixed to run on Pharo. Squeak trunk also has closures...so.. > > >> Morever, should the BlockContext class be removed too? >> > > I would like, too. The only problem is the "compatibility". What maybe can > be done is to remove the class but do something like > > Smalltalk at: #BlockContext put: #BlockClosure > > But I have no idea the impact of this.... > > >> >> Depending on answers, I will write a bug report. >> >> Luc >> >> _______________________________________________ >> 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
