Damien
I decided that living is about mistakes so I will not stress and continue to improve the platform.
And from time to time I will do a mistake and we will fix it.
I prefer to die because I have moved than because I feared to move because at the end I will die.

Stef

Le 19/2/15 18:43, Damien Pollet a ��crit��:
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���)

On 19 February 2015 at 15:05, stephan <stephan@stack.nl> wrote:
The way this was handled can be improved. It is sometimes difficult for us not in Lille
to find out what is going on.

- a specific issue name helps us notice what changes
- check where code is used. DeprecationFinder works for that
�� (and should add more repos and team projects).

And a specific one: the rename from #asSmalltalkComment
to #asComment is problematic. There are 2 kinds of thing
casually known as comments: the comment text in a method,
and the class comment.�� The method name should reflect that.

Stephan




--
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet