<<In the accounting program I have to
leave the program, locate and modify the source code, precompile the
source, compile the precompiled source, and link the application. If the
latter is what would be required with an Xtalk plugin, I don't want it.>>
Well, there is probably some middle ground. You'll never have the "edit at
runtime" scenario with a Codewarrior plugin- simply because you are compiling
the code. I would say the best scenario would be a much improved CompileIt!.
Does the system you use have a Codewarrior plugin, or does it just convert to
C on it's own and then tell you to go open Codewarrior? If there was an xTalk
preprocessor, it would at least be integrated into Codewarrior such that it
could report your errors while everything was still xTalk, and never let you
see any of the C being generated. And do everything at once: no multiple
steps for the user.
Better yet, if anyone is brave enough to write an xTalk compiler that can
call toolbox routines etc (read: modern day CompileIt!) , we'd all be able to
write our compiled apps in xTalk instead of C. Heck, we could write OpenCard
in compiled xTalk, wouldn't that be nice =)...
Anyway, it's more of a thought than a plan on my part, but I think it's an
interesting avenue...
Brian
