This sounds great guys.Stuart, are you interested in producing some Magma-Pharo package with me? If you are already advanced but still need some help let me know. Cheers.
r.
On Thu, Jul 30, 2009 at 12:52 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Wed, Jul 29, 2009 at 8:45 PM, Stuart Herring < st-lists@stuartherring.com> wrote:
On Thu, Jul 30, 2009 at 9:01 AM, Mariano Martinez Peckmarianopeck@gmail.com wrote:
Perhaps in these case, you have the same problem. What I did for Glorp,
and
it worked perfect, is to copy all the Magma methods in BlockContext
(they
should have 1 or more categorry called *Magma or something like that) to BlockClosure. In addition, I created a separate package called GlorpPharoPort with all
the
things to make Glorp work in Pharo. One of these things was these
methods
extensions to BlockClosure. Be aware this package should be loaded after the other packages.
Yes, ended up doing exactly this to get Magma working - I was going to post what I did, but I wanted to run the tests first, and changes in
Nice ;)
Now I am thinking most packages that extends BlockContext will have such problem :( However, be aware that (I think) Squeak is also trying to integrate closures (not only pharo).
some of the Socket code means that the tests also need porting, and I ran out of time.
What changes? IPv6?
Regards, Stuart _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma