Nicola Bernardini wrote:

> > Another thing I believe to be useful, is to open and close orchestra
> and
> > scores without having to restart Csound each time. In this case the
> time
> > of loading will be reduced and this will help us especially when
> writing
> > and testing new osc/scos. Any idea?
>
> well, this would imply running an eval loop and an in-line editor
> (a` la lisp, to be clear). Now *this* implies some work, especially
> considering the way the parser is presently written (and has always
> been, as far as I know): it's absolutely impossible to modify and
> maintain that section of code the way it is written. Which brings
> me to another subject: is the csound community interested in
> attempting
> a backward-compatible re-write of the parser using decent tools like
> lex (flex) and yacc (bison)? This would allow, after rebuilding the
> parser,
> much better possibilities in extending the language for important
> things like array variables, better conditionals, sub-patching
> (instrument stacking), parameter field passing with strings, numbers,
> variables, etc. Can you imagine what csound would be like with these
> constructs? It would have the same impact as switching from
> fortran-like Music V to csound itself!
>
> I am available to put some effort into this, but I would like to
> understand from this list if this is something effectively useful
> to the community (I won't do it for the sake of doing it, I don't
> care).

Very interesting...
I think that all these are very good things, of course only if backward
compatiblity with old orc/sco will be completely kept back.
BtW what are exactly lex, yacc, flex and bison? Do they work  with all
platforms and with all C-C++ compilers?
Thanks

Gabriel