Re: [octave ] LOADPATH recurses only one level of subdirectories (on network drives)

2006-02-14 Thread John W. Eaton
On 14-Feb-2006, Eric Blake wrote: | so it is a | bug in octave if it is mis-optimizing traversal in the presence of a | directory link count of 1. It might make sense, though, for cygwin to set | the link count to 0 on remote directories (rather than 1), to make it | obvious that the link count r

Re: [octave ] LOADPATH recurses only one level of subdirectories (on network drives)

2006-02-14 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 2/14/2006 7:18 AM: >>> >>>The code checks for two links (the %h) given that a subdirectory should >>>have a "." and a ".." entry. But for some reason, network drives >>>created using windows within cygwin report 1. > > Beca

Re: [octave ] LOADPATH recurses only one level of subdirectories (on network drives)

2006-02-14 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ugh - top-posting reformatted http://cygwin.com/acronyms/#TOFU According to Larrie Carr on 2/11/2006 11:25 PM: >>> Probably the code you are looking for is the function do_subdir in >>> liboctave/kpse.cc. This file contains a stripped-down version of

[octave ] LOADPATH recurses only one level of subdirectories (on network drives)

2006-02-11 Thread Larrie Carr
So the punch line is that octave will not work with network drives due to the difference on how "stat" returns the number of hard links. Octave uses stat to determine if the directory is recusible. But you can replicate the problem with using stat on the command line. $stat -c "%h %f" /cygdr

[octave ] LOADPATH recurses only one level of subdirectories (on network drives)

2006-02-10 Thread Larrie Carr
John W. Eaton wrote Probably the code you are looking for is the function do_subdir in liboctave/kpse.cc. This file contains a stripped-down version of the kpathsearch library. Most modifications were to remove TeX-specific stuff and to convert it to use std::string instead of plain C strings w