nicolas.leveille@free.fr wrote:
> > Indeed. The gcc preprocessor will have to be used on the SAOL code
> > QOrchestra generates, to include a library of standard SAOL
> > opcodes/instruments. The release of QOrchestra is now scheduled for 6
> > May.
>
> a question, why use the gcc preprocessor and not a more powerful
> preprocessor like m4? (which is installed on almost any unix machine)
Where could I find more info about m4. I have heard of it, but (IYHO) what
makes it better than gcc's.
My goals for using a preprocessor are 1) to be able to include code blocks,
2) use macro preplacement for such things as instr names; input parameters;
and code blocks, and 3) create a flexible means of routing an instr's
output to any output (outbus, spatialize, etc). Number 3 is really just a
special case of number 2, but it will also effect how instruments will be
designed more than the other macro replacement functions. I also started to
think about how to handle things like definitions needed for the global
block, but it sounds like John has a better solution with the distributed
global block idea.
There are other factors involved. Most of what is revolving around sfront
is pure 'c' and SAOL. How different is the syntax used for 'm4' from the
preprocessor used by 'gcc'? Can I translate what work I have done, or do I
need to restart? (I have not done a lot, but this is just a hobby for me,
so I don't have a lot of time to learn a new language/preprocessor).
Mike
This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 12:03:54 EST