I'm usually extremely apprehensive of changing code I don't own, to the point I ��� sadly ��� contribute nearly nothing to Pharo. Now, cleaning the platform ��� and in this case, by cleaning, I really mean hazmat suits, industrial grade acid, and flame throwers ��� is going to break things. I'm all for a process to help others follow such changes, but if we want a process to work, it has to be even simpler than not having a process. In any case I don't want to have to stress over touching platform code.
I think it would make sense to publish a configuration for DeprecationFinder in the configuration browser. Does it work on any Pharo image, or is it written on top of Moose ?
About #asComment : since class comments are free text, any string will do and there is no escapement sequences to enforce. Maybe ideally we would have string un/escaper objects responsible for translating between free text and and specific encodings (comments, strings, regexes, URLs���)