It is not what I intended. I intended plugins as a means for people doing
new opcodes to have their work usable by others without requiring Csound to
be rebuilt first, and to get around some license issues. Other than that,
the more builtins, the better. I envisaged many but not all opcodes that
start as plugins later moving into the core.

However, I have no strong objection to them all being plugins... it does
make for a cleaner separation between internals and opcodes, which is
certainly desirable, and so might help make Csound multiply instantiable.

What is your personal preference?

Original Message:
-----------------
From:  jpff@codemist.co.uk
Date: Tue, 20 Jan 2004 16:30:04 +0000
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3979] Re: csound5 - oscbnk


I would prefer as many opcodes as possible to be plugins, and only the
barest core (not sure what, but =, out for sure) remaining.  I thought
that was what was intended and is why I moved so many.
==John ffitch


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .