+ 1 Given a date and a version is a nice way to educate people to traceability.
Marcus Denker-4 wrote
I think the idea was to deprecate deprecated: so people use the one with more infos... (deprecated:on:in:)
But for small external projects, deprecated: is just fine and there are users. So I suggest we just move it out of the deprecated package and have it as a simple to use version of deprecation tagging.
It was quite a bit of work to clean the system of calls to #deprecated: http://code.google.com/p/pharo/issues/detail?id=4718
If it's an important feature of other projects (I don't see the value over the more informative version; who has a use case?), maybe the best thing is for it to be loadable but not included by default? If it's left in the image, I'm sure habit and inertia will have people continue to use it in the core image, which is not what we want.
Sean
-- View this message in context: http://forum.world.st/deprecated-in-Deprecated14-tp4107546p4108889.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.