[Octave-bug-tracker] [bug #33411] Breakpoints aren't hit with run command

[John W. Eaton]

Follow-up Comment #1, bug #33411 (project octave):

Just to clarify, the run function doesn't run other functions.  It can only
run other scripts since it sources the named file.  If you source a function
file, you will just define the function, not execute it.  So I assume that
your file foo.m is a script file.  Is that correct?

Also, if you plan to work on this, you might want to look at the functions
load_out_of_date_fcn and out_of_date_check in symtab.cc.  Those functions do
something similar to what we probably want, except that they start with an
octave_function object (which can be a script) and we only have the name of a
script file.

What we may want to do is find out if there is already a script loaded in the
symbol table from the same file that we are being asked to run, then check to
see whether the already parsed script is out of date.  If it is, we need to
parse the file again.  If not, then we should skip the parse step and execute
the octave_user_script object that we found in the symbol table.

I suppose all of that could go inside the source function itself, then both
run and source will be fixed.  Unless you think that the source function
should not bother with this optimization and should always parse the file. 
But if that is the case, then I don't see why the run function should behave
any differently.


    _______________________________________________________

Reply to this item at:

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

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