<div dir="ltr">Oh, I haven't thought about doing that trick with Symbol, seems to make a lot of sense. Maybe making Symbols unique within a package instead of globally would be enough. Still there might be a lot of work to do in order to make all tools work as expected, not sure. I'll keep this technique in mind and maybe try some experiments, thanks!</div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 13, 2019 at 2:46 PM <<a href="mailto:ken.dickey@whidbey.com">ken.dickey@whidbey.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2019-05-13 05:21, Luciano Notarfrancesco via Cuis-dev wrote: > Hi everybody, > Every now and then I wish we had namespaces. What's the simplest > namespace-like thing that could allows us to simultaneously load two > packages with clashing class names? Luciano, There are many ways to do namespaces. Perhaps the simplest is to have multiple #symbol hashmaps. You probably know that 'someSring' as always yields the same symbol. See #Symbol class>>intern: Having a uniq hashmap for each namespace gives multiple symbols with the same spelling -- one per namespace. This has also been used for multiple versions of code. Useful when debugging a new version of the debugger -- just use the old, working code to debug the new. The tools need to display symbols with some font/annotation so that you know to which namespace a symbol belongs, Code Browser needs to add methods using selectors in the proper namespace and so on. Much confusing otherwise. FYI, -KenD </blockquote></div>