In my case, the concern is detecting whether inode numbers are valid (and hardlinks might exist) or not (and filenames are assumed to map 1:1 to files) rather than vagaries like case-sensitivity that can only really be verified by specific testing in the directory you want to know about.
I asked this at Portable way to determine if two names refer to the same file? and arrived at the "check which implementation of File::Spec is in use" solution there.
If inode numbers are not valid, will plainly different files appear to have the same inode number according to stat? In that case, how do I find the path a module was loaded from? I could stat two modules from the library and make sure they have different inodes...
In reply to Re^7: File::Spec::Win32 returning different result than File::Spec when doing catfile with empty string
by jcb
in thread File::Spec::Win32 returning different result than File::Spec when doing catfile with empty string
by nysus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |