Open cenghoff opened 2 years ago
This issue also prevents customising typeextensions. )clear mytypeext←1 2⍴ 3 'aplf' ]link.create # d:/temp/linktest -flatten -fastload -source=dir -typeextensions=mytypeext ERRORS ENCOUNTERED: ⎕SE.Link.Create: Destination namespace not empty: #
I have asked cenghoff this via email:
Can you achieve what you want with something like this?
]link.create # c:\repos\tools-global-apl -flatten -fastload -source=dir
The default for typeExtensions is Default: 6 2⍴2 'apla' 3 'aplf' 4 'aplo' 9.1 'apln' 9.4 'aplc' 9.5 'apli'
Is that OK for you?
The issue is not the typeExtension. It makes no difference if I use default or not. The problem at hand is, that if I already have some stuff in the root namespace, then I cannot create a link via flatten.
I imagine the flatten argument must be taken into consideration and if that one is set, then allow a "non-empty" root namespace. However I don't know if this introduces some unforeseen side effects.
Describe the bug I use Link with flatten option, hence link into root namespace. After upgrading to v. 3.0.19 of Link it is no longer possible to do in a non empty root namespace.
This is the reported message:
I have noticed it was added to documentation, that only empty namespaces was allowed, but is this really what we want?
To Reproduce
Expected behaviour I expect to be able to link to root namespace also when it contains variables, functions, etc.
The actual use case is a situation, where I have workspace with an APL application loaded in root and want to include some additional functions to root namespace.
Session transcript See above.
Desktop (please complete the following information):
⎕SE.Link.Version
: [3.0.19]Additional context It seems to work even if root namespace isn't empty. I added a stop in line 44-45 and set emptyns.