[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49647] octave foo.m vs. octave /other/path/to
|
From: |
Mike Miller |
|
Subject: |
[Octave-bug-tracker] [bug #49647] octave foo.m vs. octave /other/path/to/foo.m |
|
Date: |
Fri, 18 Nov 2016 22:13:47 +0000 (UTC) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 |
Follow-up Comment #2, bug #49647 (project octave):
And this may be related to the fix for bug #33411. If the file does not exist
in the current directory, then it has not already been seen by the parser, and
it is sourced like the previous version of Octave. If it is in the current
directory or otherwise in the load path, then it has already been parsed, and
for some reason "source foo.m" instead invokes the function foo. That may have
been an unintended consequence of the change
http://hg.savannah.gnu.org/hgweb/octave/rev/4c080cbc4ef9
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49647>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/