Of course, I may be wrong, but I think

like that:

1) *matrices are certainly better for big matrices, e.g. quantiles

for surface responses

2) for small matrices, it's a matter of convenience

for an user: with *matrices we can't input

fun({1,2,3},...)

only b = {1,2,3}

fun(&b,....)

3) Of course I can't make cost-benefit analysis,

since costs in coding time is not on me

Oleh

On Fri, 18 Dec 2015, oleg_komashko@ukr.net wrote:

> Thank you, Sven It works with *matrices. Unfortunately, it seems, 
> there are no (yet?) defaults for [usual] matrices. Of course, it 
> has a way around, but many function calls in many situations would 
> have looked much shorter

Can you give us an idea of contexts in which you'd like to be able 
to define a default matrix argument, and where the pointer form is 
somehow unsuitable?

Allin
_______________________________________________
Gretl-devel mailing list
Gretl-devel@lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel