[Pharo-dev] Uniformizing Pharo

Camillo Bruni camillobruni at gmail.com
Mon Aug 12 21:48:17 EDT 2013


yes please! :)

On 2013-08-12, at 17:08, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:
> Hi guys
> 
> I started to be fed up about protocol inconsistencies. So I will propose a set of rules (and a tool - I'm working on it) to automatically categorize methods.
> The first on the list was printOn: in printing and I clean many methods already with a kind of happy smile on my face.
> 
> Now we discussed today with esteban for initialize* we will use 'initialization'
> I hope that this is ok for you because I'm fed up to have the following: 
> 
> 	{269->'initialization'. 248->'initialize-release'. 48->'as yet unclassified'. 15->'accessing'. 14->'private'. 12->'initializing'. 2->'instance creation'. 2->'testing'. 2->'initalize-release'. 2->'protocol'. 2->'display'. 1->'cleaning'. 1->'intializing'. 1->'like fullCopy'. 1->'keymapping'. 1->'ui-building'. 1->'initialize - release'. 1->'initialization-release'. 1->'intialize'. 1->'styling'. 1->'scrolling'. 1->'morphic ui'. 1->'world state'. 1->#'parts bin'}
> 
> Please enjoy this gift from life, I love so much 'like fullCopy' as a category for initialize that I'm a bit sad to 
> clean this kind of poem (minimal haiku) so we will keep it for us :)
> 
> Yes there is no little steps to get a bright system, every little clean is stop.
> 
> No broken window! No dirt on the floor in Pharo. 
> 
> Stef





More information about the Pharo-dev mailing list