[Pharo-dev] Uniformizing Pharo

Camille Teruel camille.teruel at gmail.com
Fri Aug 16 09:59:56 EDT 2013

Also, to prevent explosion of the number of protocol names in the image, we could agree on some naming convention.

For example, there are protocols ending with -ing and others ending with -ion: which form one should prefer?
ex: conversion vs converting, composing vs composition.

Then, when a protocol name is made of several word, should we use space or - to separate them?
ex: instance creation vs instance-creation

On 15 août 2013, at 09:35, Stéphane Ducasse wrote:

> On Aug 14, 2013, at 9:26 PM, Camillo Bruni <camillobruni at gmail.com> wrote:
>> ah looks very nice, indeed much more powerful than my hack.
>> If you have time, switch to real regular expressions, because things like 
>>> add: (MethodCategorizationRule whenSelectorMatches: 'as*' categorizeIn: #converting);
>> will easily produce false positives. For instance #assert: will end up in converting, which is not what you want ;)
>> => /as[A-Z][a-zA-Z]*/ for instance does a much better job
> Ok thanks for the idea.
> I will.

More information about the Pharo-dev mailing list