There are too many arguments in the signature of the my_inla generic. The
signature defaults to every argument in the formals, which are probably
already over-specified. Typically, one defines a generic with the formals
(x, ...), or perhaps in this case (x, model, ...), but more on that below
Unre
It seems. FYI. Gabor
[[alternative HTML version deleted]]
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Hi there,
perl6 offers with the NativeCall package a great tool to implement other
languages into perl scripts. This has already been done with python, C(++)
and perl5. For my use cases - lots of data munging and statistical analyses
(climatology/meteorology) - it would be perfect to parse data an
When someone suggests that we "might have had a reason" for some peculiarity in
the original S, my usual reaction is "Or else we never thought of the problem".
In this case, however, there is a relevant statement in the 1988 "blue book".
In the discussion of subscripting (p 358) the definition
> Henrik Bengtsson
> on Mon, 4 May 2015 12:20:44 -0700 writes:
> In Section 'Indexing by vectors' of 'R Language Definition'
>
(http://cran.r-project.org/doc/manuals/r-release/R-lang.html#Indexing-by-vectors)
> it says:
> "Integer. All elements of i must have the sam
Looks like the c(x)[...] bit used to be as.matrix(x)[...]. Not sure
why the change was made many years ago, but this was before names were
handled explicitly. It would definitely be better to not force the
duplicate, at least in the case where we are sure c() and [ would not
dispatch.
Best,
luke
Dear all,
I did some more work in this.
- put all the metadata in a dedicated subclass (see metadataclass branch in
github repository). This doesn't solve the problem.
- test the code under R 3.1.2. This gives the same problem. So this is NOT
a bug introduced by R 3.2.0 :-)
- Profiling the code.