[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47910] problem when running MXE Octave in com
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #47910] problem when running MXE Octave in command line |
Date: |
Thu, 12 May 2016 17:23:47 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 |
Update of bug #47910 (project octave):
Status: None => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
That's not the right way to run a function file.
If you want to run a script,
octave-cli foo.m
If you want to call a function,
octave-cli --eval foo
Your example is the same as running
>> foo.m
in Octave, which is evaluating a symbol "foo", which happens to be a function
in this case, and then trying to index the result with a field name of "m".
If your function "foo" returned a struct that had a member named "m", then it
would work.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47910>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #47910] problem when running MXE Octave in command line,
Mike Miller <=