lexikos wrote: ↑05 Aug 2022, 22:41
@RaptorX It is my understanding that
hard links are just the normal way that a filename is associated with data on the drive. Every file has at least one hard link, but can have multiple. The v2 installer does not explicitly use hard links to alias files; it uses
symbolic links, a.k.a. soft links.
Yes, that is correct, in my OP in github I was very careful to use the word
symlink when describing my issue to make sure he understood that the link could be resolved before passing it to AHK2Exe.
It seems that he had a misunderstanding of the issue anyways and after a few posts started referring to it as hard links. So all that is just a miscommunication issue, rather than a misunderstanding.
lexikos wrote: ↑05 Aug 2022, 22:41
The link is primarily intended for tools that need to
run scripts on either 64-bit or 32-bit as appropriate for the current OS. When compiling a script, one would generally need to make a choice between binaries based on the
target system; i.e. what will be running the script, not necessarily the system which is running the compiler.
I am of the opinion that it is still an unneeded restriction. If the Autohotkey file being sent to AHK2Exe is valid, it shouldnt be rejected. Or at least it could allow for a command line flag to force the use of a valid file that is being passed.
I do get your point though and I agree. But say (in this particular instance) that I know that the symlink is pointing to the correct
target OS and I have it already selected in vscode because I have been working with it. Why must I be forced to change my selection before compiling if I already know that my selection is correct?
While a
very trivial issue, It is a pet peeve of mine when developers (knowingly or not) force restrictions that are not really needed.
If the file is valid,
just accept it.