[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44678] Using spaces in m file names causes er
From: |
Pantxo Diribarne |
Subject: |
[Octave-bug-tracker] [bug #44678] Using spaces in m file names causes error on compile |
Date: |
Tue, 31 Mar 2015 14:51:01 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 |
Update of bug #44678 (project octave):
Status: None => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Hi,
This is not expected to work: imagine a script named "foo bar.m", in order to
run this script you would have to type "foo bar" in the terminal. This syntax
has already another meaning in Octave/Matlab language, which is "run the 'foo'
function with the string argument 'bar'". However, in Octave (not in Matlab)
you can run such script using "run ('foo bar.m')" but this is not considered a
good practice.
Now, I could check what matlab returns when you try to run (using the "run"
button in the built-in editor) such file with a space in its name. The file
name was "foo bar.m":
>> foo bar
Undefined function 'foo' for input arguments of type 'char'.
This is definitely an equally uninformative error message.
Closing bug report.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44678>
_______________________________________________
Message posté via/par Savannah
http://savannah.gnu.org/