Issue 4902 in pharo: deprecated: users should be rewritten into deprecated:on:in:

Status: Accepted
Owner: [hidden email]
CC: [hidden email]

New issue 4902 by [hidden email]: deprecated: users should be  
rewritten into deprecated:on:in:
http://code.google.com/p/pharo/issues/detail?id=4902

There are a lot of senders of deprecated: so I reintroduced the method in  
Object.
Now We should pay attention to the sender of deprecated:


deprecated: anExplanationString

        ^ self deprecated: anExplanationString on: '8 October 2011'  in: 'Pharo1.4'


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

Updates:
        Status: FixToInclude
        Labels: Type-Cleanup Milestone-1.4

Comment #1 on issue 4902 by [hidden email]: deprecated: users should  
be rewritten into deprecated:on:in:
http://code.google.com/p/pharo/issues/detail?id=4902

Attached CS does:


-> move #deprecated: out of Deprecated14 (as e.g. Zinc is using it)
-> clean all deprecated: callers but Zinc


Attachments:
        DeprecatedFix.1.cs  22.2 KB


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

Updates:
        Status: Integrated

Comment #2 on issue 4902 by [hidden email]: deprecated: users should  
be rewritten into deprecated:on:in:
http://code.google.com/p/pharo/issues/detail?id=4902

in 14373


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

Comment #3 on issue 4902 by [hidden email]: deprecated: users should  
be rewritten into deprecated:on:in:
http://code.google.com/p/pharo/issues/detail?id=4902

To be integrated later (no rush):


Sven Van Caekenberghe uploaded a new version of Zinc-HTTP to project Zinc  
HTTP Components:
http://www.squeaksource.com/ZincHTTPComponents/Zinc-HTTP-SvenVanCaekenberghe.247.mcz

==================== Summary ====================

Name: Zinc-HTTP-SvenVanCaekenberghe.247
Author: SvenVanCaekenberghe
Time: 4 March 2012, 10:35:23 am
UUID: 5ae403b7-a4cb-4ca9-a49a-0e71b6bd036a
Ancestors: Zinc-HTTP-SvenVanCaekenberghe.246

changed usage of #deprecated: to #deprecated:on:in:



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

Comment #4 on issue 4902 by [hidden email]: deprecated: users should  
be rewritten into deprecated:on:in:
http://code.google.com/p/pharo/issues/detail?id=4902

I don't understand this decision. Pharo's mandate does not include backward  
compatibility. #deprecated: was removed because all seemed agreed that we  
did not want people using it. I'm sure people will now, because it is the  
path of least resistance. Why not just force outside users to adapt, like  
*every other thing we deprecate*. Why pick this out of a hat to go against  
the policy?


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

Comment #5 on issue 4902 by [hidden email]: deprecated: users should  
be rewritten into deprecated:on:in:
http://code.google.com/p/pharo/issues/detail?id=4902

because external packages will never do that change. Even Zinc changed it  
two days ago (not yet integrated)

We don't want to be compatible, but we need to take care to not loose  
everyone in the process...


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

Comment #6 on issue 4902 by [hidden email]: deprecated: users should  
be rewritten into deprecated:on:in:
http://code.google.com/p/pharo/issues/detail?id=4902

That's what I don't understand - what makes users less likely to adapt to  
the removal of this method than the countless others that have been removed?


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