>> ... So my rule of thumb would be: As long as you're on your
>> own, do whatever you want. You want a quick hack? Go for it. But as 
>> soon as
>> you start sharing (which includes sending a CS around) I'd argue that 
>> things
>> should be classified by then. Or put differently: Nothing that ships 
>> with
>> "official Squeak" should have unclassified methods or non-descript 
>> names.
>
> I was thinking the same thing.  We could have a rule that we won't 
> incorporate any classes that are uncategorized into "official Squeak". 
>  I could add a test for this in my proposed changeset validator.  So 
> then we could have Lex's enhancement, and Richard wouldn't have to 
> worry about ever seeing uncategorized classes in base Squeak. :)


This is good idea and I like the fact that no unclassified get in.

Stef

>
> (We could also have a rule about not allowing uncategorized methods, 
> although for some reason they don't bother me quite as much, 
> especially for very small classes with only a handful of methods.)
>
> - Doug
>
>