Re: Deleting resource forks
Re: Deleting resource forks
- Subject: Re: Deleting resource forks
- From: garbanzito <email@hidden>
- Date: Fri, 12 Jul 2002 10:51:18 -0600
at 2002 07 11, 22:33 -0700, they whom i call Philip Aker wrote:
After execution, the file had no resource fork because when I tried
to open it with ResEdit, I was asked if I wanted to create one.
So what exactly do you mean when you say: "the name is deceptive"?
well, it's a semantic issue. when a fork has zero length,
does it exist? i took the documentation literally when it
said a resource fork "always exists" for HFS+. similarly if
you have a file with a zero length data fork, does that fork
exist? the way the documentation was worded seemed intended
to clarify that FSDeleteFork() didn't necessarily actually
delete the fork.
the ResEdit behavior isn't definitive, i think, because
ResEdit actually populates the resource fork with 286 bytes
of data when it offers to "create one". in ResEdit's limited
domain, an empty resource fork is not a resource fork.
also, this shell command (on an HFS+ folder) seems to
illustrate that every file has both a resource and a data
fork, regardless of whether either is empty.
ls -ld */..namedfork/data */..namedfork/rsrc
semantic, yes, but it seemed a practical distinction too,
given that rm didn't seem to behave well on the resource
fork, while cat'ing /dev/null into the fork worked smoothly.
(can anyone repeat the bizarre rm behavior i described
previously? i got an offline note from someone who
couldn't. i did my test on 10.1.4.)
--
steve harley email@hidden
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.