<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 6/20/2024 2:19 AM, Luciano Notarfrancesco via Cuis-dev wrote:
<blockquote
cite="mid:CAL5GDyqYMOUjQx-a0o8d4mL7-wK6Mc4iUnVJatLb2v_wt2vGcA@mail.gmail.com"
type="cite">
<div>
<div dir="auto">It’s up to you. I don’t do it, and i think most
people in Cuis dont do it either (perhaps becase Cuis is
smaller than other Smalltalks, so it’s less prone to name
clashes).</div>
</div>
<div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 20, 2024 at
06:39 Mark Volkmann via Cuis-dev <<a
moz-do-not-send="true"
href="mailto:cuis-dev@lists.cuis.st" target="_blank">cuis-dev@lists.cuis.st</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">From what I understand it is standard
practice to add a prefix your classes to avoid name
conflicts with classes from other packages. Is it
recommended to do this for every class you define? Are
there guidelines on choosing prefixes such as their length
(2?) and case (all uppercase?) ? Is there a list of well
known prefixes used by popular packages that we should
avoid using in our own class names?<br>
<br>
---<br>
R. Mark Volkmann<br>
Object Computing, Inc.<br>
-- <br>
Cuis-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a><br>
<a moz-do-not-send="true"
href="https://lists.cuis.st/mailman/listinfo/cuis-dev"
rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
The question is: why do names clash? I can think of two reasons:<br>
- Duplicated concepts. A redesign is in order. Each concept should
appear once.<br>
- Names are too generic. Things that are not the same are named the
same. Renaming is in order to clarify.<br>
<br>
The only times I had names clashing, and I still wanted them to
coexist was during merge of different codebases. For that, a rename
with some prefix is appropriate. Any prefix would do. It should be
as short lived as possible.<br>
<br>
HTH,<br>
<pre class="moz-signature" cols="72">--
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich</pre>
</body>
</html>