> The csys_setup() function your driver creates gets called
> part of main_initpass() (actually, the very last thing in
> main_initpass() right now) -- the way I'd prefer to add
> the functionality you added with the COMMANDLINE() macro
> is to make a copy of arc and argv[] available for reading
> by csys_setup(). Is there a reason why this wouldn't work
> for you? Let me know, and I'll figure out the best way
> to do it and add the functionality into the control driver
> in the next release ... part of the reason for making a
> copy is so that I can reclaim some slots on the command
> line for the main sa.c program to use at a later time,
> without breaking compatability ...
It sounds like your idea will be a bit more universal than mine. Have
you (or anyone else) started a list of what commandline options will be
available in the resulting sa.c program?
Also, I am still putting the finishing touches on my control driver.
Currently, it dynamically creates a SASL score. I am mostly interested
in fractals and such, so I would like to have the ability to have the
resulting sa.c program produce a different output.wav each time it is
run.
Is there anyone else that is working on something like this? I would be
more than interested in sharing what I have done so far.
Mike
This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 12:03:51 EST