Thanks for the reply. Actually the parser already exists as part of a
stand-alone executable. It has been ported to many platforms including
Classic MacOS (which to the best of my knowledge does not support stdout).
Additionally, I eventually want to select parts of the buffer to pass to
the rest of the program (or process with elisp functions then pass on
etc), which I would also like to call as a primitive (incidentally the
other program is Csound, or a branch of it called icsound).
I want to combine the functionality of csound with Xemacs to create an IDE
for csound. Is this madness?
From the name of it I assume that file-name-handler-alist exists for
this
reason (ie to handle certain files differently from standard text files if
necessary). Am I wrong? If that is its purpose, how is it used?
For more info on Csound:
http://www.csounds.com/faq/index.html#INTRODUCTION
and icsound:
http://leporello.agnula.org/~maurizio/icsound/
On Thu, 29 Aug 2002, Daniel Pittman wrote:
Make your C parser a stand-alone executable that outputs it's
results to
stdout.
Then look at `start-process' or something like that.
Daniel
--
Heu! Tintinnuntius Meus Sonat!