[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51960] mex or oct function in +package direct
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #51960] mex or oct function in +package directory that shadows Octave function only works once |
Date: |
Fri, 8 Sep 2017 11:43:50 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #4, bug #51960 (project octave):
Hmm, this is a little bit tricky to reproduce. It has to be an oct or mex file
in a +package directory that is overriding an m file function in Octave, not a
builtin.
With +foo/size.oct there is no bug, because size is a builtin:
>> foo.size
warning: function ./+foo/size.oct shadows a built-in function
ans = This is my size function
>> foo.size
warning: function ./+foo/size.oct shadows a built-in function
ans = This is my size function
With +foo/imread.mex this bug occurs, because imread is an m file function:
>> foo.imread
my imread
>> foo.imread
error: Invalid call to imread. Correct usage is:
...
And with +foo/which.oct it also occurs, because which is an m file function:
>> foo.which
ans = This is my which function
>> foo.which
error: Invalid call to which. Correct usage is:
...
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51960>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/