Am 15.08.2006 um 16:04 schrieb Richard Talbott:
> I used Royal software's hypertalk compiler to make a large number
> of XCMDs and XFCNs. I read the following to mean I will not be able
> to use them with supercard. I think my code is PPC, but that will
> be another investigation. Agreed, a recompile is needed, but at
> this time I do not know carbon or C. No sweat, one solid man week
> and I can be up to speed on the introductory stuff, it's just that
> I have an infinite number of 5-minute jobs already.

There was never a version of CompileIt for PowerPC (well, none that
shipped, though I think Tom Pittman was working on something). Also,
even if there had been a PPC version, that would definitely only have
been a Classic version, not Carbon source code. So, unless all of
your XCMDs were straight HyperTalk and you just compiled it to speed
it up (in which case you'd probably just re-use the code as is in a
modern xTalk, as all of them have gotten significantly faster and run
on much faster hardware these days), you'll have to rewrite it in C
and Carbon.

> hmmm, anyone know of a stack I can use to compile a stack scrip
> into native code for speed improvements? I wish to remain ignorant
> of the professional programmer's infinite dimensions of infinite
> dimensional space.... Laser point concentration has its advantages
> (and disadvantages... sigh).

I wouldn't bother at this point. RunRev is "virtually compiled",
which essentially means they're running some internal byte code, and
SuperCard's interpreter has seen speed-ups well beyond 800% in recent
releases, and you're running on very fast hardware these days. If
it's just speed you need, the native languages should be about
sufficient these days. There's no script compiler available at this
time as far as I know.

> "In this case, most externals designed for use with HyperCard will
> not be executable in OS X. "

Yeah. That's a problem with OS X, not with SuperCard, and it's true
for *any* xCard. The reason is simply that OS X introduced
significantly changed APIs, and that the old ones don't work on a
modern, pre-emptively scheduled OS.

Cheers,
-- M. Uli Kusterer
http://www.zathras.de