Hi Anthony,

I think you make good points but this is also a change of behavior
that hasn't thus far been noted.  But you're right in this is a bit
confusing.  The usage I was accustomed to before was having SFDIR as a
fallback, the default place to put things, but if I wanted to quickly
test a CSD, then I would use "./test.wav" as my output and put it into
the current directory.  A handy feature for me, but I do agree that
SFDIR then is pretty ambiguous as are paths in CsOptions, and that it
is strange to type something like "csound test.csd -o test.wav" and
have that output in SFDIR, while "csound test.csd -o ./test.wav" would
output in the current working directory.

I did like how it worked, but I guess I can get used to this. (Will
probably just stop using SFDIR).

Thanks for the reply!
steven


On 10/31/06, Anthony Kozar <anthonykozar@sbcglobal.net> wrote:
> Well, it depends on whether you think that is a bug.
>
> The problem is what to do when we encounter paths beginning with "./" or
> ../" in a CSD and there is no "reasonable" concept of a current directory.
> Any GUI front end started by double-clicking falls into this category in my
> opinion.  And I think paths like this should be interpreted relative to the
> appropriate search paths.  That is why I changed the function that
> determines whether a pathname is absolute or not.
>
> I wasn't really sure when I changed the code if the shell would expand ./ or
> not.  But if you think that pathnames beginning with "./" typed in on the
> commandline should be interpreted as the shell would interpret them, then I
> think we will have difficulty distinguishing between them and those that
> were read from an input file.  Plus, I am not sure that having different
> behavior depending on the source of the pathname makes sense.
>
> Besides, if you've gone to the "trouble" of setting SFDIR, then I don't
> think the output should go to the current directory.  Setting SFDIR, IMHO,
> means that the name of the output file will be interpreted relative to
> SFDIR.
>
> Anthony
>
>
> Steven Yi wrote on 10/30/06 11:13 AM:
>
> > Hi Anthony and all,
> >
> > I think one of the directory handling changes that happened in
> > envvar.c did introduce a bug, and I want to say it has to do with code
> > that did assume paths given "./" or "../" or the like were absolute.
> > What I'm experiencing is if I do something like:
> >
> > csound examples/xanadu.csd -o ./test.wav
> >
> > The wav file does not get generated in the cwd, but rather in SFDIR.
> >
> > I've taken a look to find out what's going on but haven't quite found
> > it yet.  Any suggestions?
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net