Thanks, and sorry - I missed those two "missing letter "ed" and though
you only refer to that URL for extra example code. mixsort() does it
for me.
/H
On Thu, Jan 7, 2010 at 3:50 PM, Henrik Bengtsson wrote:
> Follow up/bug:
>
> mixedsort() gets confused when there are periods in the string(s);
I had suggested two possibilities, not just mixedsort. The other was mixsort:
> mixsort("a.b.c")
[1] "a.b.c"
> print(mixsort("a"))
[1] "a"
> print(mixsort("a."))
[1] "a."
> print(mixsort("a.b"))
[1] "a.b"
> print(mixsort("a.b."))
[1] "a.b."
> print(mixsort("a.b.c"))
[1] "a.b.c"
> print(mixsort("a
Follow up/bug:
mixedsort() gets confused when there are periods in the string(s);
> print(gtools::mixedsort("a"))
[1] "a"
> print(gtools::mixedsort("a."))
[1] "a." NA
> print(gtools::mixedsort("a.b"))
[1] "a.b" NANA
> print(gtools::mixedsort("a.b."))
[1] "a.b." NA NA NA
> pr
Hello.
I'm still working on my OCaml-R binding and I get a segfault in the
GetNewPage() function of memory.c.
For the record, the OCaml-R binding seems to work fine with OCaml
bytecode. The segfault here is the main issue I have with OCaml native
code. OCaml-R can be found on the following l
This may get delayed as I am away from my usual mail system.
Since (thanks to Dirk and Charles) there is the cran2deb project giving us
most R packages in debian package format, could the alien package help?
See
http://www.linuxdocs.org/HOWTOs/RPM-for-Unix-HOWTO-8.html
John Nash
___
Hmm, have you read getCRANmirrors? It works gracefully if the
connection is down, and has been tested quite a lot
It seems you got a corrupt read from the URL: that's not reproducible
and the place to deal with that is getCRANmirrors.
Please do use an informative subject line: it makes
Full_Name: Chris Evans
Version: 2.10.1
OS: Windows XP sp3
Submission from: (NULL) (86.159.235.204)
I was on leave and using a wifi internet connection in France and got connected,
launched R (2.10.1 on Windoze XPsp3) and tried to update my packages and got:
> chooseCRANmirror()
Error in m[, 1L]
Hi,
the "Writing R extensions" manual currently advises to register a .Call
function as follows:
R_CallMethodDef callMethods[] = {
{"myCall", &myCall, 3},
{NULL, NULL, 0}
};
This produces a compiler warning, at least on my GCC, because the second
slot in the R_CallMethodDef
