Re: [Seaside Issues] Issue 797 in seaside: Seaside-JSON-Core extends BlockClosure but BlockClosure is not a portable class

> Yes, it just takes moving the extension to a platform - specific package. I know how to do that for Pharo, but I'm clueless what to do for Gemstone.
>
> On Jun 16, 2014 4:48 PM, <[hidden email]> wrote:
>
> Comment #1 on issue 797 by [hidden email]: Seaside-JSON-Core extends BlockClosure but BlockClosure is not a portable class
> http://code.google.com/p/seaside/issues/detail?id=797
>
> I guess this is a straightforward request and change. We just need to mind updating the Gemstone JSON package. There is a testcase covering this method, so it will pop up as broken when porting.
>
> --
> You received this message because this project is configured to send all issue notifications to this address.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>
> _______________________________________________
> issues mailing list
> To unsubscribe, email [hidden email]
> http://lists.seaside.st/listinfo/issues
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev