[ok now *really* to gretl-devel]
Am 06.03.2012 10:59, schrieb Sven Schreiber:
I'm wondering whether there may be a case to extend the princomp()
function somewhat to get a direct access to that (optional third matrix
parameter in pointer form for example). Sure it would be sort of
redundant from a syntactic point of view, but since those eigenvectors
have to be computed anyway it could be an efficient way to get those.
[p.s. to gretl-devel only:]
A general syntactic question about those pointer-style arguments: Given
that hansl is usually very concise, is it really always necessary to
define/initialize the object in a separate line?
What I mean is, instead of:
<hansl_snippet>
matrix argument_to_be
eigensym(foo,&argument_to_be)
</hansl_snippet>
would it be possible to do something like:
<hansl_snippet>
eigensym(foo,&[matrix myarg])
</hansl_snippet>
Note the added '[matrix ...]' -- I am not proposing to use the old
syntax and simply create the argument on the fly and guess its type,
which would not catch typos for example (if really previously defined
objects are meant).
This is really just about saving the extra line and hopefully make hansl
even more readable. I know tastes will differ here (especially those of
the C people...).
thanks,
sven