Thanks Lukas. The problem is not how to serialize them. We are in touch with Colin, and in fact we are correctly serializing MethodContext.
My question was about how to get a whole stack that doesn't change and that I can control and use it for testing. And no, I didn't see any test in Colin's serializer about MethodContext. Right now we are genereting a stack of 2 or 3 MethodsContext by hand.

On Mon, May 23, 2011 at 11:57 AM, Lukas Renggli <renggli@gmail.com> wrote:
Have a look at the serializer of Colin, it does serialize contexts.

Lukas

On 23 May 2011 10:33, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
> Hi guys. We need to do some test to serialize a MethodContext to a file,
> materialize it, and then compare it to the original. One of the problems we
> face is that some values in the MethodContext are changed so it is difficult
> to test.
> So...what we would like is to get a "bottom" MethodContext that we can ask
> #sender, and to that one #sender, and like that....and the whole stack
> should cannot be changed.
>
> Another problem is that I cannot do a #deepCopy on a MethodContext because
> #basicNew: throws errror.
>
> Is this possible?
>
> Thanks in advance,
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>



--
Lukas Renggli
www.lukas-renggli.ch




--
Mariano
http://marianopeck.wordpress.com