Issue 4483 in pharo: clean up #hasNewFinalization

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 4483 in pharo: clean up #hasNewFinalization

pharo
Status: Accepted
Owner: [hidden email]
Labels: Milestone-1.4

New issue 4483 by [hidden email]: clean up #hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

hasNewFinalization

--> all current vms support it.

--> senders can be cleaned


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo

Comment #1 on issue 4483 by [hidden email]: clean up  
#hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

Checked with Igor: Seemingly Eliot's VMs do *not* support it.

So removing it would have a certain effect...


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo
Updates:
        Status: ReviewNeeded

Comment #2 on issue 4483 by [hidden email]: clean up  
#hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

1) change the Finalization Project to not check for the VM change.
       - FileIn attached file WeakArray class-finalizationProcess.st
       - Do "WeakArray restartFinalizationProcess." in the postscript.

2) changeset CleanFinalization.1.cs removes all the compatibility code.

Remember: the image will not work on other VMs....

Attachments:
        CleanFinalization.1.cs  2.4 KB
        WeakArray class-finalizationProcess.st  440 bytes


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo
Updates:
        Cc: [hidden email]

Comment #3 on issue 4483 by [hidden email]: clean up  
#hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

Igor can you review this change


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo
Updates:
        Labels: Type-Cleanup

Comment #4 on issue 4483 by [hidden email]: clean up  
#hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo

Comment #5 on issue 4483 by [hidden email]: clean up #hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

Eliot's VMs do not support this. So, if we remove it, we should clarify  
then to people to use VMs built on our servers.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo
In reply to this post by pharo
Updates:
        Status: FixReviewNeeded

Comment #7 on issue 4483 by [hidden email]: clean up  
#hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo
Updates:
        Status: OnHold

Comment #8 on issue 4483 by [hidden email]: clean up  
#hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo
Updates:
        Labels: Milestone-3.0

Comment #9 on issue 4483 by [hidden email]: clean up  
#hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4483 in pharo: clean up #hasNewFinalization

pharo
Updates:
        Labels: MigratedToFogBugz

Comment #10 on issue 4483 by [hidden email]: clean up  
#hasNewFinalization
http://code.google.com/p/pharo/issues/detail?id=4483#c10

Issue migrated to https://pharo.fogbugz.com/f/cases/4530

--
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

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