Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!kth.se!cyklop.nada.kth.se!d88-jwa
From: d88-jwa@nada.kth.se (Jon W{tte)
Newsgroups: comp.sys.mac.programmer
Subject: Re: stdio, THINK C and APPLs
Message-ID: <1990Dec27.201132.19383@nada.kth.se>
Date: 27 Dec 90 20:11:32 GMT
References: <VLADIMIR.90Dec23224539@prosper.EBB.Eng.Sun.COM> <1990Dec24.182548.17958@svc.portal.com> <1990Dec27.183436.3786@ux1.cso.uiuc.edu>
Organization: Royal Institute of Technology, Stockholm, Sweden
Lines: 20

In article <> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes:

>>>If the data fork assumption is correct, is this The Way It Should Be?  How
>>This is The Way It Should Be!
>Horse puppies!

Well, Apple has told us not to use the resource fork for data, but
just to use the Resource Manager calls. Opening the resource fork as
a normal data file might be too tempting for some :-)

As it says in TechNote <something> - the OpenRF calls are only
provided for people who want to a) try and correct corrupted resource
forks or b) copy a resource file in whole.

This is just as well done using Mac ToolBox calls.

							H+
-- 

Jon W{tte, Stockholm, Sweden, h+@nada.kth.se