map{ some_statement } some_range while some_condition;
[download]

You have a block there :), and the keyword goes in front too - might just as well do

do { some_statement for some_range } while some_condition;
[download]

At least, that's me.

As far as the symlink is concerned, it's as easy as ln -s . foo (for which there actually are legitimate uses every once in a blue moon - I've used it). There are also a million other scenarious that require to decide on an individual basis whether a symlink is to be followed or not.

Another thing I just remembered is AFS (Andrew File System) - a hugely useful truly distributed filesystem, which, to work as it does, has the unfortunate consequence that even absolute paths can mean different things under different conditions.

If you fiddle long enough, you can come up with some pretty far out pathological cases on Unix. File::Find will handle them correctly - modulo what few bugs may be left, of course, but that's the advantage of having code reused and retested millions of times.

Makeshifts last the longest.