Now let me answer the 2nd question of Chris

> 2. Did you look at the modules in MacPerl that do the same thing, with
> an eye toward compatability of interfaces?

  Yes I did and I did check File::Copy myself as well.  As a matter of fact
File::Copy appears to be MacPerl-compliant already.  In a course of writing
MacOSX::File, 95% of the time is spent on research and just 1% is spent on
actual coding (Don't you think this retio, research vs. coding is getting
worse as time goes by?)

on 02.1.9 8:44 AM, Ken Williams at [EMAIL PROTECTED] wrote:
> Also, File::Copy should copy files correctly on MacOS (X and otherwise),
> though I'm not sure whether it currently does so.  Do you know the
> situation?

  The fact remains that /bin and /usr/bin ignores Carbon world.
  My understanding is that Darwin does not have to care MacOS world; it is
left to Carbon that does.
  Therefore I belive File::Copy should do what /bin/cp does while mine does
what /Developer/Tools/CpMac does.
  IMHO, a module like this should have been done by Apple...

Dan the PM Writer

Reply via email to