sorry, I somehow missed the second part of your mail before replying ;) Not sure if this is a good idea as it looks a bit like a monkey patch... Would it actually work with MC? Because the class name from the class definition of MC would still return 'BlockClosure', I assume. Adrian On Aug 10, 2009, at 08:42 , Adrian Lienhard wrote:
BlockContext is not used anymore but is kept in the image for backward compatibility for a while (so that packages like Seaside still load as they define extension methods on BlockContext).
If there are missing methods in BlockClosure let us know.
Adrian
On Aug 10, 2009, at 08:24 , Miguel Enrique Cobá Martinez wrote:
El lun, 10-08-2009 a las 01:19 -0500, Miguel Enrique Cobá Martinez escribió:
http://code.google.com/p/pharo/issues/detail?id=1058
Can this two classes be merged (the share 80% or more than methods and several are identical, maybe were copied) and then (assuming that the BlockClosure will be the enduring):
Smalltalk at: #BlockContext put: BlockClosure
This way several packages that extend BlockContext will work in the new closure vm, for example Magma.
What are the pros/cons of this change?
If feasible, will be marked as Milestone-1.0?
Ramiro Diaz Trepat and Mariano MartÃnez Peck commented on the magma mailing list that they successfully loaded magma on a pharo image by copying the extensions added by magma to BlockContext to the class BlockClosure. It appear that the code worked ok. Maybe with this change it wouldn't be necessary to modify magma (Chris Muller should speak about this). That can be the case for a lot of packages and will ease the integration and "certification" of several packages on pharo.
See:
http://lists.squeakfoundation.org/pipermail/magma/2009-July/ 001321.html
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project