>Only problem is that CompileIt! code is 68k, and also not all that well
>suited for writing a preprocessor (IMO). I don't think it would be worth the
>trouble for the novelty of doing it with CompileIt!. Not that a part of me
>doesn't like the idea- I just don't think it's the best choice.
Hi,
I think writing a preprocessor is rather easy with CompileIt -- after all
you can do arrays with it, and it has chunk expressions all ready. Will
simplify parsing to some degree. But I think we should use a language that
we'll be able to use for a PowerPC version, too, as in the long term 680x0
is as dead as a Dodo.
Maybe you could write the converter using CompileIt And then write the
next version of the converter using the converter? Anyway -- C/C++ looks
like it'll be faster. If you care about my $0.02, I'd suggest writing a
simple application that takes a file name and converts that file to C/C++
code (or whatever in-between form you desire, egcs tokens or what have
you). When that works it won't be hard to adapt the code to use CW's
plug-in stuff, and if you use pure ANSI C wherever you can, it'll even be
portable, which will yield an MPW tool or even a plug-in for some Unix
compiler.
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
