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

[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: Avinoam Kalma
Subject: [Octave-bug-tracker] [bug #51960] mex or oct function in +package directory that shadows Octave function only works once
Date: Tue, 2 Jan 2018 00:25:12 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36

Update of bug #51960 (project octave):

             Assigned to:                    None => jwe                    

    _______________________________________________________

Follow-up Comment #7:

Trying to see the origins of this problem, I have found that in 4.2.1, using
the script desribed in the first comment, I get


>> temp.imread
my imread
>> temp.imread
my imread


This has been broken in
http://hg.savannah.gnu.org/hgweb/octave/rev/551fa3879615


>> temp.imread
ans =

error: octave_base_value::print (): wrong type argument 'mex function'
>> temp.imread
ans =

error: octave_base_value::print (): wrong type argument 'mex function'


In http://hg.savannah.gnu.org/hgweb/octave/rev/2d4a7ae1f6cd appears difference
between first and second call:


>> temp.imread
ans =

error: octave_base_value::print (): wrong type argument 'mex function'
>> temp.imread
ans =

error: octave_base_value::print (): wrong type argument 'user-defined
function'


This has been reported in bug#51295, and has been fixed in
http://hg.savannah.gnu.org/hgweb/octave/rev/ffd27f53fc79, but the fix is good
for the first call, the second call finds the wrong function.

I hope this information will help to fix this bug.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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