[Octave-bug-tracker] [bug #40064] Legend "interpreter" property not working correctly

[Glenn Golden]

Follow-up Comment #34, bug #40064 (project octave):

Thanks for your response, Mike. I'm happy to have the opportunity to debate
this in some detail to get a good resolution. In my view, it's more important
than is perhaps being appreciated.

I disagree with most of your points but would like to address them in detail
in an in-depth writeup, rather than superficially one comment at a time. In
order to do so, I would like to ask again for answers to the three
straightforward questions asked earlier (comment #30). Without that
information it is difficult to respond intelligently in depth.

Quickly commenting on your example script though: No disagreement at all that
that script has no compatibility issue in either direction (O->M or M->O). But
in my view, that example is entirely unrelated to the issue at hand in this
ticket, since it explicitly sets the interpreter type for the legend object.
The issue in the ticket (regarding both M/O compatibilty and Octave's own
documentation) is the behavior in the absence of an explicit interpreter
setting for the legend() object, in which the object falls back on either
user-supplied or hardwired defaults.

Again, if I can get answers to the three questions asked previously, I'll
respond in more depth and address all the points you brought up.

Thanks.

    _______________________________________________________

Reply to this item at:

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

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