[Octave-bug-tracker] [bug #47687] automatic broadcasting for assignment operations

[Lachlan Andrew]

Follow-up Comment #5, bug #47687 (project octave):

> So unless Octave gets a new way to set warnings within the scope
> of the caller only (different from the "local" option in
> warning), such warning will be of quite limited use.

Developing a new warning system is on my "pipe-dream to-do list", mainly
motivated by our previous discussion on this topic.  When you distinguish
"local" from "the scope of the function", what is the difference?  Does
"local" mean just the current stack frame and "scope" mean the stack frame and
all descendants?


I'm not yet convinced that the usefulness of a broadcast warning would be all
that limited.  Compare the number of core functions that use broadcasting with
the number that use '#' for comments...

Anyway, I think a much better solution would be to replace "automatic"
broadcasting with explicit broadcasting with a non-intrusive syntax.  The
underlines in comment #3 were missed.  I as suggesting "underline /",
"underline *" etc for operations with broadcast.  Any other combination of
symbols would be fine.  (It is a pity that Octave uses ! and # to duplicate
Matlab symbols, so there are fewer for new language features, but that's
another discussion.)  Was that discussed at OctConf too?

    _______________________________________________________

Reply to this item at:

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

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