On Tue, Apr 10, 2012 at 12:52:53PM -0400, Michael Gogins wrote:
> Wait a minute -- by "preprocessor" you mean the bin attribute in the
> CsScore tag?
> 
> Wait again -- I think you mean look for a Lua file matching a score
> file, and evaluate that.

No score preprocessor but `csound_pre.lex'.

> In either case, the lua_opdef calls are necessary because the actual
> Lua opcodes have to be bound to a C++ Lua opcode stub which is called
> by Csound.

In general, I know how to work `LuaCsound.cpp'.
The idea is filename.lua or `lua_include "..."' (perhaps it is better).
The lua file contains the code for the new opcode. We can eval it
during the orc-preprocessing and we have the csound instance
for appendOpcode. I'll try in the next days when I will have time.
It is only a starting point or simply a "it works" (or "I'm wrong").

> We should talk about this more, especially since Csound6 may change
> how much of this kind of thing is done.

Of course; my msg is only a trigger, however I'm weak without a test.

tito


------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net