[Cuis-dev] Naming conventions

[Erik Stel]

Hi Ken,

I think you just answered my question ;-).

It can indeed be a Pharo ’thing’. In Pharo (default image) you have class names like ’ZnWebSocket’. It represents a WebSocket and comes from the ‘Zinc’ framework. I think it coexisted with WebSocket for some time (the later is no longer part of the default Pharo image). Also ‘MCPackage’ is a package from Monticello (the versioning system). A full name like ‘MonticelloPackage’ would have solved that issue of name conflict I suppose.

Regards,
Erik


> On 27 Apr 2020, at 17:13, ken.dickey at whidbey.com wrote:
> 
> On 2020-04-27 07:28, Erik Stel via Cuis-dev wrote:
>> Hi,
>> Short question:
>> Also using Pharo, I’m used to creating classes with prefixed names
>> because of possible name collisions. What is the Cuis take on these
>> prefixes? I do not see any prefixes being used in the
>> packages/features I’m using at the moment.
>> Regards,
>> Erik
> 
> Examples?
> 
> What is the context?
> 
> Not being a Pharo user, I have no idea what you are talking about.
> 
> Typically, one wants to use meaningful names in a way that orients one and makes code reads like sentences.
> 
> Note that the base Cuis image typically has between 500 and 600 classes.  The latest Pharo base image has over 9000 classes.  Perhaps the (pre)fix is for a Pharo problem..
> 
> -KenD
>