>What I'm really fishing for is something to replace my old crusty CompileIt!.
>The gain comes in a couple of flavors depending on who you are. If you are a
>C programmer, it means that you can do your work which normally would require
>working in C in xTalk. If you are a casual xTalk scripter, it makes "real"
>programming more accessible to you, because you can now accomplish the same
>things as C programmers without learning a new language. It's no longer
>scripting, it's just another realm that could benefit from xTalk.
Brian,
well, if you make it less like Assembly language (which is how most parts
that CompileIt uses to interface to the toolbox look) and more like
HyperTalk, I won't mind. But if OpenTalk becomes as fast as we hope and as
good, we could possibly stay with interpreted code.
>I'll be tempted to work on it since we have an interpreter for the taking,
>but I can't make any promises, and I don't claim it to be of direct benefit
>to OpenCard development, other than being another tool based partly on
>OpenCard...
I see nobody who's stopping you -- go ahead!
>Really, I would just love for xTalk to get some recognition in the
>Codewarrior world. Very few C programmers consider xTalk a serious language
>if they know of it at all, which is sad. They might be swayed if they saw it
>elegantly accomplishing the same stuff they do with nasty looking C.
I'd love it. But I have to admit I prefer C to CompileIt. It's concept is
much more clear when it comes to anything that goes beyond what HyperTalk
can do.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
