Thu 02 Mar 2017 04:20:17 PM UTC, comment #7:
@Kai,
seems fine.
A few comments: Using isjava.. whether a variable contains...
But it is not only applicable to variables
I would write
With isjava it is possible to check whether an expression
results in a java object
and if so class returns the name of its java class.
The next example is really great!
Sentence: But ambiguities may arise...
is not so good.
I think, the point is that Double is converted into double
when used as a parameter.
Below:
I would rewrite "method and constructor parameters"
as "parameters of methods and constructors"
Well, whether calling static methods and getting static fields
in a special way is a workaround... hm..
I think, it is the way it is done.
Note that also javaObject
is a kind of workaround since java.long.Double(3.4)
does not work (as it does in matlab)...
I would not write about "empty brackets"
it is the empty array I think.
You write "It is not recommended",
but in fact, the user has no choice.
One could write: be careful: ... [] has type double whereas null has no type.
I would talk about debug_java right after mentioning exceptions.
Also I would not write
"In octave it is possible to provide..."
but just "Octave provides ..."
I think for methods and fieldnames one should provide links
als you do for the other functions.
also I have forgotten to mention, that octave also allows to display constructors.
|