On second thought, maybe that's what Steven actually meant.

Languages that do that do that these ways:

C/C++:
    INCLUDE path environment variable or -I compiler flag
    #include 

Java:
    Packages must be in one to one correspondence with directory structure
    import xxx.yyy.zzz;

Python:
    Packages directories must be in PYTHONPATH environment variable or
sys.path variable.
    import xxx

What you (and perhaps Steven) are suggesting is like Python. I think this is
best.

============================================
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: "Pedro Kroger" 
To: "Csound Developers Discussion List" 
Sent: Wednesday, December 17, 2003 4:43 PM
Subject: [CSOUND-DEV:3796] Re: REVIEW


> * Michael Gogins (gogins@pipeline.com) wrote:
> > 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.
>
> what about something like "import fluid" and csound would look in the
> opcodes path. Would be much more flexible and portable this way.
>
> Cheers,
>
> Pedro Kröger
>

Hi All,

Yes, this was what I was thinking.  I found my original email here:

http://eartha.mills.edu:8000/guest/archives/CSOUND-DEV/log0312/msg00017.html

I still haven't created the csoundFindFilePath function but will do so
when I'm finished up here in Boston.

As for Richard Dobson's comments on a default load directory, yes! 
Csound would need a SYSTEM_LIB variable (that's a bad name, anyone
please offer a better one) so that any libraries in that directory are
auto imported. This would be nice for not only compiled libraries but
also user-defined opcodes as Matt suggested a while back.

steven


On Wed, 2003-12-17 at 18:00, Michael Gogins wrote:
> On second thought, maybe that's what Steven actually meant.
> 
> Languages that do that do that these ways:
> 
> C/C++:
>     INCLUDE path environment variable or -I compiler flag
>     #include 
> 
> Java:
>     Packages must be in one to one correspondence with directory structure
>     import xxx.yyy.zzz;
> 
> Python:
>     Packages directories must be in PYTHONPATH environment variable or
> sys.path variable.
>     import xxx
> 
> What you (and perhaps Steven) are suggesting is like Python. I think this is
> best.
> 
> ============================================
> 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: "Pedro Kroger" 
> To: "Csound Developers Discussion List" 
> Sent: Wednesday, December 17, 2003 4:43 PM
> Subject: [CSOUND-DEV:3796] Re: REVIEW
> 
> 
> > * Michael Gogins (gogins@pipeline.com) wrote:
> > > 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.
> >
> > what about something like "import fluid" and csound would look in the
> > opcodes path. Would be much more flexible and portable this way.
> >
> > Cheers,
> >
> > Pedro Kröger
> >
> 
>