Welcome!

By registering with us, you'll be able to discuss, share and exchange private messages with other members of our community.

SignUp Now!

Does the PLUGIN command know about directory aliases?

May
12,621
152
Code:
v:\> plugin /L plug:\SysUtils64.dll
TCC: (Sys) The specified module could not be found.
 "plug:\SysUtils64.dll"

v:\> dir /k /m /a:-d plug:
2023-06-05  17:52         164,352  4Console64.dll
2022-10-20  16:53         158,720  4threads64.dll
2023-05-31  11:59         272,384  4utils64.dll
2023-06-05  11:27         143,360  4wt.dll
2023-05-14  11:57         195,584  SysUtils64.dll

v:\> alias plug:
d:\data\tccplugins
 
Nope. But you can push your filename through @TRUENAME to canonicalize it.
 
Nope. But you can push your filename through @TRUENAME to canonicalize it.
Easier to use the literal true name, or, at the command line, just press <Tab>. But why not supported? I would have guessed directory aliases aren't specifically built-into (or not) every command; I thought it a much more general mechanism.
 
I think it basically comes down to whether the command calls QueryTrueName() (or whatever its TCC-internal equivalent is.) Some commands do, some don't.
 
Easier to use the literal true name, or, at the command line, just press <Tab>. But why not supported? I would have guessed directory aliases aren't specifically built-into (or not) every command; I thought it a much more general mechanism.

Guessed wrong - directory aliases are built in to every command that need them. (PLUGIN /L doesn't really qualify as a need.)

The only generic directory alias code is for tab completion.
 

Similar threads

Back
Top