[Octave-bug-tracker] [bug #60482] hist() misses error for non-numeric input

[Nicholas Jankowski]

Follow-up Comment #4, bug #60482 (project octave):

for my second request in the last comment, i submitted a low-priority wishlist
bug #60487.

since nothing parses that char string until set, I think the only way to catch
this would be for hist or bar to check that first string against every
possible valid character input for that space. the latest dev version of hist
mentions that 'the full list of properties is documented at @ref{Patch
Properties}'.  I currently see about 50 properties on that list [1].  

Set also allows partial property name matching when it's unambiguous, so
'facenormalsmode' and 'facenormalsm' would be valid, but not 'facenormal'
since that could be either of two properties. for hist to check string
validity then, it would have to compare with every valid property and
variation thereof.  

Don't really see a way forward here with our current version of hist accepting
graphics properties, short of an effort to come up with a
'check_valid_property' function that could be called in places like this and
kept up to date on its own.

[1] https://octave.org/doc/latest/Patch-Properties.html

    _______________________________________________________

Reply to this item at:

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

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