I thought that someone would bring up the 'why not use File::Spec*?' question. The simple answer is that I wrote that module to support older perl installations. In fact I haven't gotten around to using File::Spec - nor even base yet. I certainly intend to do so. Does catfile() take care of both data and resource forks on MacOS? Peter Prymmer On Fri, 15 Jan 1999, Chris Nandor wrote: > At 00.43 -0500 1999.01.09, Peter Prymmer wrote: > >BTW (changing the topic slightly to X-platform cp -r implementations) > >does anyone see a problem with something like this apart from > >symlinks on UNIX (hence it is cp_r and not cp_R)? In glancing through > >perlport it appears that using '/' as a separator on > >Acorn RISC OS path names is sometimes acceptable, and if need be it > >could be changed to use '.' if $^O eq 'riscos'. > > A wwek after the original post I get around to reading ... > > Why not just use File::Spec->catfile($srcdir, $src_file) instead? > > -- > Chris Nandor mailto:pudge@pobox.com http://pudge.net/ > %PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10 1FF77F13 8180B6B6']) > ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch