[Octave-bug-tracker] [bug #45864] problem with mkoctfile

[Mike Miller]

Update of bug #45864 (project octave):

                Category:                    None => Octave Function        
                Severity:              3 - Normal => 1 - Wish               
                Priority:              5 - Normal => 3 - Low                
              Item Group:                    None => Feature Request        
                 Release:                   4.0.0 => dev                    

    _______________________________________________________

Follow-up Comment #2:

Mario did ask about this on #octave first, and jwe suggested that he provide a
patch or report this in some way, so here we are! :)

I think his suggestion is reasonable, that mkoctfile should attempt to unload
the oct-file before compiling it to allow it to be overwritten on operating
systems where the file is locked when in use.

I can create a simple oct-file on Linux, prove to myself that the file is open
by Octave after the first time the function is called, and is no longer open
if I run "clear -f funcname". If this is done automatically by mkoctfile, this
might help the majority of cases.

It might not help in cases where a single oct-file defines more than one
function, I can't seem to get the oct-file to unload on Linux unless I do a
complete "clear -f".

    _______________________________________________________

Reply to this item at:

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

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