[Octave-bug-tracker] [bug #53084] CamelCase graphic property names for Matlab Compatibility

[Rik]

Follow-up Comment #8, bug #53084 (project octave):

Is there really no hope?  Sad!

More seriously, can we not be at least a little better than Matlab?

In the predicate tests the underscore has been useful in denoting things which
are Octave specific.  Hence, 'isscalar' is jammed together because the
functionality is also available in Matlab under that name.  But,
'is_sq_string' uses underscores to indicate that this is an Octave-specific
function.

Also, I have been wanting to redo the graphics properties in the documentation
to not have quotes around them, but just use @code.  One of the things I came
across was how to logically handle CamelCase within graphic properties.

If things were logical, the CamelCase would occur where there was a break in
the variable.  Of course, that is not how Matlab did it.  They chose to break
wherever two English words meet.  Hence there is the single graphics property
"LineWidth".  It becomes an issue when you start trying to set defaults.  For
example: 


set (groot, 'DefaultLineLineWidth', 1)


I would prefer to write


set (groot, 'DefaultLineLinewidth', 1)


where it is clear that there are three objects being combined: 1) "Default" to
set a default property, 2) "Line" to specify an object type, and 3)
"Linewidth" to specify the name of a property.

This will always work since we allow any casing form for the set operation,
but will it be more or less confusing because I am not using the form
"LineWidth" which is elsewhere in the documentation?



    _______________________________________________________

Reply to this item at:

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

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