[Octave-bug-tracker] [bug #40452] explicit clear will not clear function entered on the command line

[anonymous]

Follow-up Comment #2, bug #40452 (project octave):

Thanks Philip Nienhuis, for taking the time to look into this. 

As regards your first question, have I tried "clear -f": yes, see command #6
in my OP; no effect either.

Wrt your side remark, I have no idea why 'function foo "nop"; endfunction'
causes syntax complaints for you: I can define and execute this foo on 3.6.2
and 3.6.4 without complaints. But of course the precise content of foo is not
important here, your suggestion produces the same result.

I upgraded to the newest version packaged for Debian, 3.6.4 (testing and
unstable), and I can confirm the bug like you did on that version on Windows.
Unfortunately even Debian-experimental does not have a newer version, so I'll
wait until 3.77 has led to a new stable release and is packaged. Glad to hear
the bug has been squashed already and can be closed.

Could you just check if 3.7.7 has also corrected the following bug, which
seems also somehow related to symbol look-up:


>> function [retval] = foo (); retval = 1; end
>> type foo
error: type: 'foo' undefined
>>

If 3.7.7 does not show the function definition as it should, I might open a
second bug-report.

Thanks again! Octave has become a really valuable piece of software for me.

Adrian


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/