Re: New Mac port of Inform


Wed, 29 Mar 1995 19:49:14 GMT

In article <3l7tch$dq6@wanda.pond.com>,
Matthew Russotto <russotto@wanda.pond.com> wrote:
>}(I ask because I keep thinking I should write a *morally correct* Z-code
>}interpreter shell -- that is, one which can import a z-code file, thus
>}producing a stand-alone application. The stand-alone app would then be
>}able to create save files that you can double-click on, and basically
>}act sensibly.)
>Unfortunately, with the advent of the Fat Binary, the obvious way of
>doing this doesn't work anymore. Probably the right way to do it now

Umm, it definitely is a bit more difficult, but it by no means
impossible. What you are referring to is putting the datafile in the
datafork, and the resources (including 68K code) in the resource fork.
Since PowerPC native code (using CFM/SOM..) is in the data fork, you think
that that means that you can't still use the data fork for other things.
That's incorrect. I know that there is some sort of "offset" to where the
PowerPC code begins, so you can still use the data fork for other things.
The offset/length are definitely in the 'cfrg' resource, but I don't know
if anything else needs to be done while compiling. Basically, it looks
like a very small bit of more calculation is needed, but nothing complex.

Anyhow, hopefully if anyone implements this idea, they'll still
distribute the Zcode data file independently...

-- 
unknown@guest.apple.com		Apple II Forever
These opinions are mine, not Apple's.