Re: [mdt-papyrus.dev] Papyrus naming convention Util vs Helper

["Christian W. Damus" <give.a.damus@xxxxxxxxx>]

Oh, also, I would suggest that helpers need not be stateful. They could just be stateless algorithms (classic strategy pattern).

@Camille:  I don't know how valuable it would be to refactor anything for this, given how pervasive the mismatching of these names is.  I wouldn't ask for it, but nor would I be opposed.

Christian 

On Monday, 24 November 2014, Christian W. Damus <give.a.damus@xxxxxxxxx> wrote:

Hi Benoit,

For what it's worth, I see the distinction the same way that you do.  For example, EMFHelper is misnamed.  I cannot answer your specific question about guideline, though, except to remark that I haven't seen any.  I nominate your definition as our guideline.

Christian 

On Monday, 24 November 2014, MAGGI Benoit <Benoit.MAGGI@xxxxxx> wrote:

Hi team,

 

Is there a rule for naming convention of Util vs Helper?

I didn’t find any reference in https://wiki.eclipse.org/Development_Conventions_and_Guidelines

 

For me :

 *A utility class is :

-          final

-          Not instantiable  (private constructor)

-          All methods are public static

Whereas

*A helper  is :

     -  public constructor

     - not static methods

     - methods can be public or private

 

ð  A utility class is stateless vs a helper is stateful

 

Did I missed something ?

Is there any eclipse rules for helper?

 

Regards,

Benoit Maggi