On 20 September 2011 22:43, Mariano Martinez Peck <marianopeck@gmail.com> wrote:if you look at the problem in wider perspective, then right question
>
>
> On Tue, Sep 20, 2011 at 10:37 PM, Igor Stasenko <siguctua@gmail.com> wrote:
>>
>> Hmm,
>> storing (and then restoring) weak containers as they are , i don't see
>> anything special which must be done there.
>>
>> The special logic how to deal with weak containers are still remains
>> same, as long as you correctly restoring the object,
>> and as long as this logic is correctly written. So, i cannot see what
>> Fuel needs to do special with weak containers.
>
> Yes, we thoght the same. But we wanted to ask just to be sure...
> Bill said the same, so we all agree :)
>
>
>>
>> You may need to deal with storing instances of WeakRegistry, since it
>> registers itself into WeakDependents array,
>> which is scanned for finalization. So, you have to make sure that if
>> WeakRegistry instance was registered in weak-dependents
>> array, then you should also register it when restoring it back. (and
>> if it was not registered - then of course not register).
>>
>> But WeakRegistry is a regular object (not a weak container by itself,
>> and only indirectly it using
>> weak containers by delegation).
>
> Yes, thanks for the pointer.
to ask, is how to deal
with objects which are register themselves in global facilities, like
weak finalization,
startup/shutdown lists etc.
For those objects you need to have special (de)serialization cases.
But for objects with particular format (weak) you don't have to do
anything special.
-->
>>
>> On 20 September 2011 20:55, Schwab,Wilhelm K <bschwab@anest.ufl.edu>
>> wrote:
>> > Good question. �I *think* the answer is to take the referenced objects
>> > across as one normally would, and then wrap them in a weak collection (if
>> > that is what was serialized). �If one had only a weak collection holding the
>> > objects, they will be short-lived. �However, something like a registry
>> > should be able to save/re-loaded, probably much like Dolphin's STBProxies:
>> > the effect of serializing the weak collection includes running some code to
>> > recreate conditions as needed.
>> >
>> > Looking forward to a lively debate...
>> >
>> > Bill
>> >
>> >
>> >
>> >
>> > ________________________________________
>> > From: pharo-project-bounces@lists.gforge.inria.fr
>> > [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez
>> > Peck [marianopeck@gmail.com]
>> > Sent: Tuesday, September 20, 2011 1:38 PM
>> > To: Pharo Development
>> > Subject: [Pharo-project] Should a serializer do something in particular
>> > with � �weak references?
>> >
>> > Hi guys. Martin and I were discussing whether we should do something in
>> > particular in Fuel with Weak references, such as WeakArray. Should we
>> > serialize it the same way we serialize all objects, or should we do
>> > something special? �what could be the impact of materializing such weak
>> > references in a new image for example?
>> >
>> > Thanks your sharing your thoughts.
>> >
>> > --
>> > Mariano
>> > http://marianopeck.wordpress.com
>> >
>> >
>> >
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>
Best regards,
Igor Stasenko.