[Octave-patch-tracker] [patch #8303] vectorized parcellfun and pararrayfun

[Olaf Till]

Follow-up Comment #11, patch #8303 (project octave):

I meant that we should only change the user interface of pararrayfun, although
the code of the file parcellfun.m might also need to be patched. I did not yet
study the patch code, it might be possible that the above is not feasible;
then we have a problem.

What regards passing 'as is', you won't convince me. This is not so much a
matter of code complication, but rather of maintaining a standard user
interface for this standard problem. Passing of unchanged additional arguments
can be necessary at many places (optimization, ODE integration) and none of
these functions provides passing additional arguments itself nowadays (or
shouldn't, there might be relics), since the standard user interface for this
problem is using anonymous functions. Also, if the arguments to be passed 'as
is' are, e.g., 'a', 'b', and 'c', then writing


pararrayfun (4, @ (x, y) user_func (x, y, a, b, c), array1, array2,
"Vectorized", ..., IdxDimensions, [d1, d2])


does not seem less clean to me than 


pararrayfun (4, user_func, array1, array2, a, b, c, "Vectorized", ...,
IdxDimensions, [d1, d2, 0, 0, 0])



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?8303>

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