[Octave-bug-tracker] [bug #32083] nested functions and developers sources

[John W. Eaton]

Follow-up Comment #4, bug #32083 (project octave):

I think things will work the same in 3.0.x as 3.2.x, but note that nested
functions are not supported.  Previously, Octave would silently treat them as
subfunctions.  For example, try this with 3.0.x:


function nested_functions (txt)
 x = 1;
 subfun1 (txt)
 function subfun1 (txt)
   disp (txt)
   x
 end
end


Calling this with


nested_functions ('foo')


I see


-foo
error: `x' undefined near line 6 column 4
error: called from:
error:   /scratch/jwe/build/octave/nested_functions.m at line 6, column 4
error:   /scratch/jwe/build/octave/nested_functions.m at line 3, column 2
octave3.2:2> type nested_functions
nested_functions is the user-defined function defined from:
/scratch/jwe/build/octave/nested_functions.m
verbatim-

But I see now that the functions are no longer being properly coerced and
instead that there is a parse error.

So, should we just fail for nested functions, or coerce them to subfunctions
(some may work that way, some will not).  In your example, they all do have
"end" statements, so the error seems wrong.  But I think we should still warn
about functions that are recognized as nested but actually handled as
subfunctions.

    _______________________________________________________

Reply to this item at:

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

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