Re: Help sought understanding shorthands wrt modules/packages

[Gerd Möllmann]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> The reason why I think shorthands don't address that problem is pretty
>> simple, according to me again: The underlying one obarray can only
>> contain one name per symbol at a time.  So, whatever name lands in the
>
> I thought CL packages had the same problem: you can't (globally) have
> two packages with the same name.

That's true, in this case that's a problem with package names.  I guess
everything having a name can conflict with the same name being used by
someone else.  But,

- You can handle it with rename-package.  I've used that in CMUCL, while
  working its CLOS implementation), to load two versions of PCL in the
  same image at the same time.

- There is an extension "hierarchical packages" which gives packages a
  tree structure.  It's more or less like with Java packages.  An
  implementation on top of standard packages isn't very hard.
  
https://cmucl.org/docs/cmu-user/html/Introduction-To-Hierarchical-Packages.html

>         Stefan "Trying hard not to get pulled into this discussion"

C'mon :-)