---- Original Message ----
| Originally Posted by Steve Fabian
| The PDIR command, when using NO options, does report the target of
| junctions. (I run WinXP, which has only junctions, not symlinks). If
| you explicitly enumerate the reporting fields, you can include
| @junction[*] or @symlink[*] as a reporting field. The function you
| requested is thus already a built-in.
Thank you for your response, Steve, but I am aware that those two functions exist, the problem is that it is two functions!!! And the function that I wrote that I referred to in my original request does nothing more than combine the outputs of the @Junction and @SymLink functions in an @If function; I do not care whether it is a junction or symbolic link; I only care that it is linked and where-to (just like in the "dir" and "pdir" commands with no field-code options); and again, this not a real big deal, just a minor (and rather silly in my eyes) irritation...
---- End of Original Message ----
I fully agree with your frustration. I don't (yet) have access to TCC on Vista or 7, thus I have not tested %@junction[symbolic_link], but assuming that it is analogous to @symlink behavior (i.e., if @junction's parameter is anything else than a junction, the function value is an empty string), you could simply create a UDF (see linked_to below) whose value is the concatenation of these two functions, without the need to use @if. I presume this is functionally equivalent to the UDF you created. Alternately, you can just use the @truename function, but beware of its use on a mapped network drive.
BTW, please do not quote the signature line - when posts are replied to by email, the email client truncates the response at the signature mark. I had to copy your response manually.