Fixed MKLINK /D

May 31, 2008
382
2
#3
Why do you want to create a (useless) link to a nonexistent directory?
I want to link targets that will come, like external drives and such, things that aren't yet physically attached. Unlike CMD's MKLINK /D, which creates a directory symlink to a (non-existent) target, TCC's MKLINK /D creates a file link to a (non-existent) target.
 

rconn

Administrator
Staff member
May 14, 2008
10,753
97
#4
I want to link targets that will come, like external drives and such, things that aren't yet physically attached..
I think you're trying to redefine a CMD bug as a feature, but I'll take a look at it. (IMO 99.99% of the time that would be a user error, not a desire to define a link to an imaginary-but-maybe-I'll-create-it-sometime-in-the-future directory.)
 
May 31, 2008
382
2
#5
Thank you for taking a look at it. I'm definitely in the 0.01% of your estimates and the use case I mentioned is a real one. I grew up on *nix systems where it is accepted practice to define "forward-pointing" symlinks, for instance, in conjunction with directories that services, not humans, create. Unlike *nix symlinks, which are "genderless", Windows makes a distinction between "directory" and "file" symlinks. CMD's MKLINK preserves that distinction.