Paul writes: > The obvious thing to do is to populate @ARGV some other way > than dropping files on a droplet. Perl can deal with symbolic > links just fine once it knows their paths. Well, I'm unconvinced. Here's why. First, in the example I was thinking of there were no dropped files, I used FSpIterateDirectory and it resolved the symbolic links. OK, not conclusive, but then I tried simple file tests on a hard coded path to one of my alias files. The -l returns true, but -f is clearly acting on the file pointed to by the alias... I tried several kinds of file access operations and they all acted on the pointed-to file, not the alias file... Though, none of my experiments included Mac I/O toolbox calls, so I'll stop just short of saying you're wrong... [wink] jay ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch