| Re: [mdt-papyrus.dev] Papyrus naming convention Util vs Helper |
|
Hi, There’s indeed no such convention in Papyrus yet. However, Helpers and Utils (Misnamed or not) have been used a lot in different places (Including
external components based on Papyrus), so any refactoring, while OK, should ensure the backwards compatibility for a couple of years at least (i.e. it is ok to deprecate EMFHelper in favor of a new EMFUtil, but not to remove it for at least a few versions). Regards, De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian W. Damus 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
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 |