Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Should be a hint on it's own!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Should be a hint on it's own!
Authored by: mj on Jul 22, '03 01:40:53PM
It turns out Rob already has posted a hint about this here, and there's an interested comment at the bottom about using the '..namedfork' route to get at any named fork.

You're right about there being some overhead with a resource fork. When you 'create' a resource fork with ResEdit, it adds a header to the fork. But every file does automatically have a resource fork that you can read from and write to, it just normally has length 0, i.e. no header info.

Michael

[ Reply to This | # ]