Compiled files ignore aliases

Compiled files ignore aliases

[Sebastian Gniazdowski]

Hello,
this is probably expected as aliases are applied on parsing time. But
maybe this wasn't yet recognized?

% cat 2test-script.zsh
#!/bin/zsh
alias autoload="echo Hello; autoload"
#autoload() { echo "Hello"; builtin autoload "$@" }
source "./test-script.zsh"
echo "|"${functions[abc]}"|"


% cat test-script.zsh
#!/bin/zsh
echo "Hello from script, will call a builtin"
autoload abc


Output when using alias in 2test-script.zsh and test-script.zsh is
compiled (there is .zwc file):
% ./2test-script.zsh
Hello from script, will call a builtin
|builtin autoload -X|

Output when using function in 2test-script.zsh:
% ./2test-script.zsh
Hello from script, will call a builtin
Hello
|builtin autoload -X|


Any way to have aliases working when sourcing .zwc file?

Best regards,
Sebastian Gniazdowski

Re: Compiled files ignore aliases

[Bart Schaefer]

On Feb 5,  4:33pm, Sebastian Gniazdowski wrote:
}
} this is probably expected as aliases are applied on parsing time. But
} maybe this wasn't yet recognized?

This is as expected, yes.

} Any way to have aliases working when sourcing .zwc file?

Typically one needs "zcompile -U" to turn OFF the aliases when creating
the .zwc file.  However, no function, zcompiled or otherwise, will use
aliases that are created after the function body is parsed.

What this means is:  The aliases have to be defined in the shell that
executes the zcompile command.

Re: Compiled files ignore aliases

[Sebastian Gniazdowski]

Yes I thought about it and it's reasonable, though unsymmetrical. Zwc
changes things, there isn't full symmetry when sourcing file already
parsed or not, but see *. The "reasonable" is that parsing probably
does lookup each word in a hash table to see if there is an alias for
it. Compiling means skipping that time consuming process. So compiling
is maybe all or maybe mostly about ability of ignoring aliases. In my
project I'm being close to able to fully switch to function shadowing,
the only juggling is about compdef which isn't builtin, but that's too
handable by function shadowing (will have to wrap function by
function). Plugin architecture may be simply extended by constraint
"expect no aliases" and that's all, it's a luck that (*) plugin isn't
"a file to source", it's a software package which may have
constraints.

Best regards,
Sebastian Gniazdowski

Re: Compiled files ignore aliases

[Bart Schaefer]

On Feb 5,  6:24pm, Sebastian Gniazdowski wrote:
}
} Yes I thought about it and it's reasonable, though unsymmetrical. Zwc
} changes things, there isn't full symmetry when sourcing file already
} parsed or not, but see *. The "reasonable" is that parsing probably
} does lookup each word in a hash table to see if there is an alias for
} it. Compiling means skipping that time consuming process.

By analogy, "alias" in shell is more like "#define" in C.  Once you've
compiled, the macro expansion is already done and doesn't happen again.

You can intentionally trigger alias expansion by using "eval", which is
(in this analogy) re-compiling at run time.