Moving C++ in the direction of m-files

[Rik]

6/9/17

jwe,

Coders who are moving from Octave's m-file language to writing .oct files,
or contributing to core Octave, face a huge learning curve.  It's not just
that the language, C++, is different, but without reading all of the header
files it is hard to know what functions are available.  Often there is an
analog in the Octave language that is available in C++, but because we use
different naming schemes it is again difficult to find these functions
short of reading the header files.  Some examples are is_empty and
is_cellstr which have analogs of isempty and iscellstr.  How would you feel
about renaming the obvious analogs to match the Octave language names?

--Rik