[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: disallowed characters in file names
|
From: |
Dmitri A. Sergatskov |
|
Subject: |
Re: disallowed characters in file names |
|
Date: |
Thu, 27 Apr 2006 15:47:41 -0600 |
On 4/27/06, Quentin Spencer <address@hidden> wrote:
> I was recently trying to get the octcdf toolbox in octave forge working
> properly with 2.9.5 (see the recent traffic on the octave-forge mailing
> list regarding this), and I found that the .oct file that contains most
> of the functions in the toolbox can't be found because it contains a '-'
> character in the file name. Here's an example:
>
> $ locate ov-netcdf.oct
> /usr/libexec/octave/site/oct/api-v18/i686-redhat-linux-gnu/octave-forge/ov-netcdf.oct
> $ octave -q
> octave:1>which("ov-netcdf");
> which: `ov-netcdf' is undefined
>
> At the same time, running the which command on any other file in that
> directory works. A file name with a '-' character is fairly common in
> Linux, but I can see why that particular character in a file name would
> be problematic for the octave parser. My question is, is this a bug or a
> feature?
>
Why should not it be parsed as "ov - netcdf" (i.e. variable ov minus
variable netcdf)?
Similar problem occur with the filenames that just a number
(e.g. you cannot have a script named 20040427.m).
> -Quentin
>
Dmitri.
--