[Cuis-dev] Naming conventions

[giorgio ferraris]

I developed long long ago (circa1990..) an ORM  FWK in VisualSmalltalk that
I evolved  up to now on VisualSmalltalk (I have still a product developed
in VS installed at customer site) , but also in VW (and, long time ago in
VA). Being a persistency framework, classes have names like Connection,
Transaction, etc.  I was lucky because VW had namespaces, so my clean names
survived against namespaces names of other packages... and in VA I survived
because they names are prefixed, but this was pure lucky  ....

ciao
giorgio

On Mon, Apr 27, 2020 at 5:52 PM Luciano Notarfrancesco <luchiano at gmail.com>
wrote:

> I also dislike prefixes a lot. But fortunately name clashes are less
> common in Cuis because there are not as many classes as in Pharo.
> Personally, I’d love to have namespaces, or have class names be local to a
> package.
>
> On Mon, 27 Apr 2020 at 10:46 PM, giorgio ferraris via Cuis-dev <
> cuis-dev at lists.cuis.st> wrote:
>
>> Hello,
>> prefixes have a long story, in use also on  VisualSmalltalk or SmalltalkV
>> long, long time ago. Not having namespaces on many Smalltalk dialects makes
>> prefix the only (ugly) solution.
>> The resulting names are horrible, I personally dislike it a lot, but
>> class' names clashing is something that could easily happens.
>>
>> ciao
>>
>> giorgio
>>
>>
>>
>> On Mon, Apr 27, 2020 at 5:34 PM Erik Stel via Cuis-dev <
>> cuis-dev at lists.cuis.st> wrote:
>>
>>> 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
>>> >
>>>
>>> --
>>> Cuis-dev mailing list
>>> Cuis-dev at lists.cuis.st
>>> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>>
>> --
>> Cuis-dev mailing list
>> Cuis-dev at lists.cuis.st
>> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20200427/5f6884ea/attachment.htm>