[Octave-bug-tracker] [bug #48774] Functions for moving statistics

[Rik]

Follow-up Comment #29, bug #48774 (project octave):

@Juan: Regarding programming strategies in core Octave, there is no simple
answer as to the best approach.  Octave should strike to have code which is
readable and maintainable, but it also needs to balance that with performance.
 The two goals are often in opposition.

If the only thing being implemented was a jump table then it would be fine to
use the original strategy.  But, the current function *does* require more
checking based on the type of Endpoint chosen.  For example, if the user
specifies a numeric fill value then one can't use [arg "_bc"] to construct a
valid function name so that is one special case.  Similarly, when the
"Endpoint" property is "discard" there is no actual discard_bc necessary, but
one does have to adjust various internal variables so that the correct length
output is generated.  Once several of the input values required identifying
and having different actions the dispatch table no longer made sense, at least
too me.

I'm not opposed if you want to re-work the input validation, as long as the
user-visible goals of functionality and performance are unchanged.


    _______________________________________________________

Reply to this item at:

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

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