<div>On Sun, Jun 23, 2024 at 11:44 Andres Valloud via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>> wrote:<br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">What is a "program"?</blockquote><div dir="auto"><br></div><div dir="auto">Not sure what you’re thinking… and I guess I should say “exactly!”. The association between a name and a concept depends on context, you can’t expect me to know what kind of “program” you’re talking about without context.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)" dir="auto"><br> <br> On 6/22/24 8:50 PM, Luciano Notarfrancesco via Cuis-dev wrote:<br> > I think it is normal to have name clashes in big systems with a global <br> > namespace, it happens in natural languages as well (and in some <br> > languages a lot more than in english or spanish). I appreciate the <br> > simplicity of not having namespaces, but I think using longer names with <br> > extra words is not a good solution. Even in a base image as small as we <br> > have in Cuis there are some important names already taken like Object, <br> > Set and Point. Not being able to use Set is particularly annoying, since <br> > there’s no other name for sets… but well, it’s ok, it could be worse (in <br> > a system with 10k classes, for example)<br> > <br> > On Sun, Jun 23, 2024 at 05:58 Juan Vuletich <<a href="mailto:juan@cuis.st" target="_blank">juan@cuis.st</a> <br> > <mailto:<a href="mailto:juan@cuis.st" target="_blank">juan@cuis.st</a>>> wrote:<br> > <br> > __<br> > On 6/20/2024 2:19 AM, Luciano Notarfrancesco via Cuis-dev wrote:<br> >> It’s up to you. I don’t do it, and i think most people in Cuis<br> >> dont do it either (perhaps becase Cuis is smaller than other<br> >> Smalltalks, so it’s less prone to name clashes).<br> >><br> >> On Thu, Jun 20, 2024 at 06:39 Mark Volkmann via Cuis-dev<br> >> <<a href="mailto:cuis-dev@lists.cuis.st" target="_blank">cuis-dev@lists.cuis.st</a> <mailto:<a href="mailto:cuis-dev@lists.cuis.st" target="_blank">cuis-dev@lists.cuis.st</a>>> wrote:<br> >><br> >> From what I understand it is standard practice to add a prefix<br> >> your classes to avoid name conflicts with classes from other<br> >> packages. Is it recommended to do this for every class you<br> >> define? Are there guidelines on choosing prefixes such as<br> >> their length (2?) and case (all uppercase?) ? Is there a list<br> >> of well known prefixes used by popular packages that we should<br> >> 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 href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a> <mailto:<a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a>><br> >> <a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br> >> <<a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a>><br> >><br> > <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<br> > appear once.<br> > - Names are too generic. Things that are not the same are named the<br> > same. Renaming is in order to clarify.<br> > <br> > The only times I had names clashing, and I still wanted them to<br> > coexist was during merge of different codebases. For that, a rename<br> > with some prefix is appropriate. Any prefix would do. It should be<br> > as short lived as possible.<br> > <br> > HTH,<br> > <br> > -- <br> > Juan Vuletich<br> > <a href="http://cuis.st" rel="noreferrer" target="_blank">cuis.st</a> <<a href="http://cuis.st" rel="noreferrer" target="_blank">http://cuis.st</a>><br> > <a href="http://github.com/jvuletich" rel="noreferrer" target="_blank">github.com/jvuletich</a> <<a href="http://github.com/jvuletich" rel="noreferrer" target="_blank">http://github.com/jvuletich</a>><br> > <a href="http://researchgate.net/profile/Juan-Vuletich" rel="noreferrer" target="_blank">researchgate.net/profile/Juan-Vuletich</a> <<a href="http://researchgate.net/profile/Juan-Vuletich" rel="noreferrer" target="_blank">http://researchgate.net/profile/Juan-Vuletich</a>><br> > <a href="http://independent.academia.edu/JuanVuletich" rel="noreferrer" target="_blank">independent.academia.edu/JuanVuletich</a> <<a href="http://independent.academia.edu/JuanVuletich" rel="noreferrer" target="_blank">http://independent.academia.edu/JuanVuletich</a>><br> > <a href="http://patents.justia.com/inventor/juan-manuel-vuletich" rel="noreferrer" target="_blank">patents.justia.com/inventor/juan-manuel-vuletich</a> <<a href="http://patents.justia.com/inventor/juan-manuel-vuletich" rel="noreferrer" target="_blank">http://patents.justia.com/inventor/juan-manuel-vuletich</a>><br> > <a href="http://linkedin.com/in/juan-vuletich-75611b3" rel="noreferrer" target="_blank">linkedin.com/in/juan-vuletich-75611b3</a> <<a href="http://linkedin.com/in/juan-vuletich-75611b3" rel="noreferrer" target="_blank">http://linkedin.com/in/juan-vuletich-75611b3</a>><br> > <a href="http://twitter.com/JuanVuletich" rel="noreferrer" target="_blank">twitter.com/JuanVuletich</a> <<a href="http://twitter.com/JuanVuletich" rel="noreferrer" target="_blank">http://twitter.com/JuanVuletich</a>><br> > <br> > <br> -- <br> Cuis-dev mailing list<br> <a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a><br> <a 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>