Issue 6403 in pharo: handle obsolete classes in MessageSend >> value and value:

Status: Accepted
Owner: [hidden email]
Labels: Type-Bug Milestone-2.0

New issue 6403 by [hidden email]: handle obsolete classes in  
MessageSend >> value and value:
http://code.google.com/p/pharo/issues/detail?id=6403

this fix adds test to MessageSend value messages to do not send messages to  
obsolete classes




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

Updates:
        Status: FixReviewNeeded

Comment #1 on issue 6403 by [hidden email]: handle obsolete  
classes in MessageSend >> value and value:
http://code.google.com/p/pharo/issues/detail?id=6403

SLICE-Issue-6403-handle-obsolete-classes-in-MessageSend-gtgt-value-and-value-PavelKrivanek.1


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

Comment #2 on issue 6403 by [hidden email]: handle obsolete  
classes in MessageSend >> value and value:
http://code.google.com/p/pharo/issues/detail?id=6403

do the same for WeakMessageSend

SLICE-Issue-6403-handle-obsolete-classes-in-MessageSend-gtgt-value-and-value-PavelKrivanek.2


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

Comment #3 on issue 6403 by [hidden email]: handle obsolete  
classes in MessageSend >> value and value:
http://code.google.com/p/pharo/issues/detail?id=6403

required for Pharo Kernel shrinking


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

Updates:
        Cc: [hidden email]

Comment #4 on issue 6403 by marianopeck: handle obsolete classes in  
MessageSend >> value and value:
http://code.google.com/p/pharo/issues/detail?id=6403

mmmmm this looks like a workaround for me. Maybe at some point we do want  
to receive notifications for obsolete classes?
maybe the real fix is to fix the CLIENTS of the notifications so that they  
properly handle obsolete classes?


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

Comment #5 on issue 6403 by [hidden email]: handle obsolete  
classes in MessageSend >> value and value:
http://code.google.com/p/pharo/issues/detail?id=6403

yes, it is a partial workaround. It is required because of system  
announcements. To fix clients is only a partial solution too, we need to  
rewrite obsolete mechanism.


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

Updates:
        Status: Integrated

Comment #6 on issue 6403 by [hidden email]: handle obsolete classes  
in MessageSend >> value and value:
http://code.google.com/p/pharo/issues/detail?id=6403

in 2.0 223


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