Re: No os.copy or lfs.copy?
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
- Subject: Re: No os.copy or lfs.copy?
- From: David Dunham <david@...>
- Date: 2008年4月10日 02:42:36 -0700
On 7 Apr 2008, at 23:10, gary ng wrote:
what is the problem of read then write other than it
may be a bit slow ?
Because it doesn't duplicate Mac OS X resource forks associated with
files?
David Dunham Macintosh Game Developer
GameHouse Studios +1 206 926 5722 www.gamehouse.com
"They said it couldn't be done but sometimes it doesn't
work out that way." -- Casey Stengel