octave-bug-tracker
[Top][All Lists]
Advanced

[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: Sat, 17 Dec 2016 20:35:45 -0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0

Update of bug #49647 (project octave):

                Category:                    None => Interpreter            
              Item Group:                    None => Regression             
                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #1:

I can confirm this difference / possible regression between 4.0.3 and 4.2.0.

I think this change can be explained by or is related to the following
difference in behavior:


## Octave 4.0.3
>> ls foo.m
foo.m
>> source foo.m
>> which foo
'foo' is a command-line function

## Octave 4.2.0
>> ls foo.m
foo.m
>> source foo.m
error: 'x' undefined near line 2 column 3
error: called from
    foo at line 2 column 2
>> which foo
'foo' is a function from the file
/home/mike/src/octave/default/+build-default/foo.m



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49647>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]