WeakArray class>>#finalizationProcess

Hello,

I just noticed that WeakArray class>>#finalizationProcess won't compile with
the with the assignment to block args set to off.

Is it okay to change that in the preferences or is the finalization process
broken then?

Kind regards,
      Markus


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

There were some notes traded by Eliot, on  
WeakArray>>#finalizationProcess between Stephane, Marcus Denker,  
Michael Rueger, Adrian Lienhard on this topic between march 26th -  
April 2nd.

Stephane said he was gong to review some changes sets from Eliot about  
this issue.

On 15-Apr-09, at 11:14 AM, Markus Fritsche wrote:

--
=
=
=
========================================================================
John M. McIntosh <[hidden email]>
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
=
=
=
========================================================================




_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Normally we should remove all the argument assignment.
I just did not get the time to go over the next batch.

Stef
On Apr 15, 2009, at 8:42 PM, John M McIntosh wrote:


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Stéphane Ducasse <[hidden email]> wrote:

>> There were some notes traded by Eliot, on
>> WeakArray>>#finalizationProcess between Stephane, Marcus Denker,
>> Michael Rueger, Adrian Lienhard on this topic between march 26th -
>> April 2nd.

Was this conversation off-list? I can't find it here, on squeakvm or
squeak.general (or my eyes get old) ;-)

> Normally we should remove all the argument assignment.
> I just did not get the time to go over the next batch.

Well, I would have made it on my own (the pharo web image I'm on only
complained about the progressbar and imagesegment methods), but this one
explicitly stated that WeakArray (and therefor anything "weak") breaks if
the assignment is deleted (and it would be pointless to nil a temp val, I
agree), so I'm curious.

Btw., Is there a Closure-FFI somewhere? I tried to load the vanilla
FFI-Kernel-ar.8.mcz (and thereafter fixing the ExternalType method) but that
seriously killed my image (not sure if anything else interferred). And I
think it was the combination of WeakArrays not being weak and something of
the FFI-package. But I'm not sure, so I don't want to rant (let's say it
just happened coincidentally ;)).

Regards,
      Markus



_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>>>
> Was this conversation off-list? I can't find it here, on squeakvm or
> squeak.general (or my eyes get old) ;-)

I just forward it to the list.
We were also checking how we can keep up with the changes of eliot.
I should have a look carefully at them.

>> Normally we should remove all the argument assignment.
>> I just did not get the time to go over the next batch.
>
> Well, I would have made it on my own (the pharo web image I'm on only
> complained about the progressbar and imagesegment methods),

Strange I fixed those ones. Can you check if you have the same problem  
in the latest?

> but this one
> explicitly stated that WeakArray (and therefor anything "weak")  
> breaks if
> the assignment is deleted (and it would be pointless to nil a temp  
> val, I
> agree), so I'm curious.

See the other email :)

> Btw., Is there a Closure-FFI somewhere? I tried to load the vanilla
> FFI-Kernel-ar.8.mcz (and thereafter fixing the ExternalType method)  
> but that
> seriously killed my image (not sure if anything else interferred).

Torsten sent us a loadFFI now available in scriptLoader in one the  
latest updates.
Can you check?

> And I
> think it was the combination of WeakArrays not being weak and  
> something of
> the FFI-package. But I'm not sure, so I don't want to rant (let's  
> say it
> just happened coincidentally ;)).

If you can reproduce that with the latest (updated image).
Let us know. We are chasing bugs now.

Stef

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Stéphane Ducasse <[hidden email]> wrote:

> Strange I fixed those ones. Can you check if you have the same problem  
> in the latest?

It could have happened that I did overwrite those by loading new PolyMorph
packages.

> See the other email :)

Merci!

> Torsten sent us a loadFFI now available in scriptLoader in one the  
> latest updates.
> Can you check?

Seems to work well. Thanks for the pointer.

> If you can reproduce that with the latest (updated image).
> Let us know. We are chasing bugs now.

Nope, working now I think.


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Btw, if anyone interested, i explored what the finalizationProcess
does in the past..
and found some things i don't like.
Maybe now in Pharo, you can cosider about fixing/improving this stuff.

http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-July/119052.html
http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-July/119054.html

2009/4/16 Markus Fritsche <[hidden email]>:


--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>> Strange I fixed those ones. Can you check if you have the same  
>> problem
>> in the latest?
>
> It could have happened that I did overwrite those by loading new  
> PolyMorph
> packages.

for the progressbar probably. I ask gary to check that.

Cool
I recompile the image again and fixed some points.

stef


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

We are always interested in better solutions.
Do you have code and got good feedback?

Stef



_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2009/4/16 Stéphane Ducasse <[hidden email]>:
> We are always interested in better solutions.
> Do you have code and got good feedback?
>
Nope :)
But i can write one. Currently, the problem is that i don't know when
i have time to do it :)



--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Apr 16, 2009, at 5:49 PM, Igor Stasenko wrote:

> 2009/4/16 Stéphane Ducasse <[hidden email]>:
>> We are always interested in better solutions.
>> Do you have code and got good feedback?
>>
> Nope :)
> But i can write one. Currently, the problem is that i don't know when
> i have time to do it :)

This is not currently for me. This is endlessly :)
So I try to take one item on the list of stuff that I should do
  and do it but the list is huge. :)
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project