[Octave-bug-tracker] [bug #42432] Error with octave when using from Perl via Inline::Octave

[Mike Miller]

Follow-up Comment #8, bug #42432 (project octave):

I just noticed that a viable workaround is to use the hack of prepending a
statement so that Octave knows that stdin is a script, not a function file:


$ echo "function x = myfunc (u) x = u + 1; endfunction; myfunc(3)" | octave
warning: function name 'myfunc' does not agree with function filename ''
error: 'myfunc' undefined near line 1 column 42
$ echo "1; function x = myfunc (u) x = u + 1; endfunction; myfunc(3)" |
octave
ans =  4


This seems eminently simple and consistent with the way that Octave already
handles function files and script files. Can we just close this with the
wisdom that inline scripts passed to stdin should start with a
non-function-declaration statement?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?42432>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/