[Octave-bug-tracker] [bug #40664] Inconsistent handling of N-dimensional RGB images

[Adam H Aitkenhead]

Follow-up Comment #6, bug #40664 (project octave):

Matlab's implementation for gray2ind works for ND arrays, we can't say if
that's through accident or intent.  Whether other functions work properly for
ND or not would have to be checked individually.  But either way, if
equivalent Octave functions can be written which do handle ND arrays
correctly, then there is no downside to allowing it.  If that ability is
documented and clear to anyone wishing to use it, then all is good.

Input checks which block valid (although perhaps not common) uses of a
function seem like a recipe for frustration with little benefit in return.  If
a user unwittingly inputs an ND array to rgb2ind or ind2rgb then the lack of
an error message is unlikely to be a problem for them.  They might even think
'That's cool, Octave still meaningfully processes that unusual data.'

The use of ind2rgb and rgb2ind needn't be limited to the capabilities of other
read/write image functions.  There are other more general uses - which is how
I came across this issue in the first place.  (Also, the current
implementation of ind2rgb blocks the use of 4D images.  It can only handle 2D
or 3D RGB images.)



    _______________________________________________________

Reply to this item at:

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

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