[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: |
Rik |
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 13:56:29 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #6, bug #51960 (project octave):
There are several extant bugs on 'which', 'classdef', and 'help' about the
path not being worked out properly for classes and packages.
If you try 'which foo' for a package dir +foo you get
'foo' is a built-in function
This is clearly not right, but probably indicates something about why built-in
functions generate a shadowed warning, but m-files don't. I'm guessing that
the path lookup is correct before the m-file in +foo has been executed. When
you request the function the very first time it has to be parsed, etc., and an
entry in the symbol table is constructed. My guess is that the 'file'
variable, or whatever it is, in the constructed symbol table entry is
incorrect.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51960>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/