Michael Gogins wrote:
> What is your motive here? Why kind of musical things are you hoping to
> accomplish that the current setup doesn't do for you? If I knew your
> use cases I could think about this better.

I don't have problems because I can write external opcodes in C code.
When I see a possibility, I propose an idea. Stop.

> But I don't want to hide things. I want to see them. I am serious
> about this. One of the major pains in my life has been pieces that
> used to work that don't work any more, and it's always some stuff in
> some other file that has gone missing, or is now in a different
> directory, or the protocol has changed, or something. I want
> everything in one file for one piece.

I have never proposed an incompatible change with the old csd files.
The idea is to add a feature and not remove your code. I appreciate
and respect your work.

Steven Yi wrote:
> One of the things I've contemplated is this kind of thing where
> opcodes written in other languages could be kept sort of hidden, such
> that users would not see lua code, just know that there is some opcode
> called foo that could be C, Lua, Java, etc.  I prefer this to seeing
> code directly mixed into Csound ORC code.  Tito: is this what you were
> thinking?

Yes, it is the point. Perhaps a `somelang_include' and/or an init.langext
file in INCDIR etc.

tito

ABEND

------------------------------------------------------------------------------
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