Re: [ruby-fltk-devel] Browser support

[Takaaki T. <tt...@ja...>]

At Mon, 3 Sep 2001 21:00:17 -0700 (PDT),
Kevin Smith wrote:
> > In this case, It is a disadvantage that Proc, Thread and
> > IO objects can't be serialized.
> 
> Interesting approach. Do you think this is better than just
> passing a VALUE and keeping a copy for ourselves? What are
> the advantages?

If we keep a copy of VALUE, we would have the difficulties of
the object chain and memory management. I'd like to avoid these
difficulties. So I suggested serializing the object.
If we deal with serialized object, we can pay attention to only
string object, and we don't need to consider those difficulties.
This is the advantage.

But we can't use this approach to implement the callback functions.
It is because we must deal with Proc object after all.
Though I suggested that we pass the Array object to the user data
of the callback function, that suggestion has same difficulties.
For example, how do we mark the Array object. One solution is your
idea that we store those Array objects somewhere. Now I don't know
how/when do we remove those objects from the store.
But I will adopt this approach to implement callbacks.
-- 
Takaaki Tateishi <tt...@ja...>