On Sat, Dec 12, 2009 at 3:59 PM, Marcus Denker <denker@acm.org> wrote:

On Dec 12, 2009, at 3:56 PM, Mariano Martinez Peck wrote:

>
>
> On Sat, Dec 12, 2009 at 3:53 PM, Marcus Denker <denker@acm.org> wrote:
> 11097
> -----
>
> Issue 1577: � � clean isSpecialWriteBinding (again)
> Issue 1585: � � More random dead code removal (76 unsent method removed)
>
>
> Marcus, when you this kind of removal (unsent methods), do you check also on Dev and Web image? or just core ?
>
right now I only check the core... :-)

But the methods removed are of the kind that they really should not be part of a public API....

IMHO we should also check senders in Pharo and Pharo Web. Pharo core in itself is nothing. Pharo is the platform for other tools. We have the dev and web image. We should take care about the packages that are loadable in Pharo. I am not saying not to remove the method, but at least, to check in dev and web images and if there are senders, send an email to the developers/maintainers notifying about this change. Even if the messages shouldn't be part of the API. With this we avoid possible DNU at runtime. Not all the external packages covers a good percent of tested code in their unit tests.

Cheers,

Mariano
�
And should we remove too much: bringing back is simple.

� � � �Marcus
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project