If by import you mean in the orchestra file something like "import
c:/csound/opcodes/fluid" where "fluid" stands for "fluid.dll" on Windows and
"fluid.so" on Unix/Linux/Cygwin, I think that's an excellent idea.

============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================


----- Original Message ----- 
From: "stevenyi" 
To: "Csound Developers Discussion List" 
Sent: Wednesday, December 17, 2003 11:02 AM
Subject: [CSOUND-DEV:3790] Re: REVIEW


>
> > > g) Moving of opcodes to loadable is largely done, but there still
> > > remains examples that can be moved
>
> While the moving of opcodes is largely done, I want to reiterate my
> proposal for the mechanism of loading libraries by using an import
> statement and load paths versus using the current --opcode-lib
> commandline flag.  (I can repost that email if requested).   Using
> import statements and not using system-specific library names (.so,
> .dll, .dylib) will allow for greater portability of CSD/ORC files, and
> explicitly listing what opcode libraries are imported I think makes for
> easier figuring out for end-users which opcodes are coming from what
> library.
>
> steven
>