Re: [Rd] RcppArmadillo compilation error: R CMD SHLIB returns status 1

2011-12-07 Thread Douglas Bates
On Dec 6, 2011 8:30 AM, "Duncan Murdoch" wrote: > > On 05/12/2011 1:22 PM, Paul Viefers wrote: >> >> Dear all, >> >> running the example by D. Eddebuettel ( http://dirk.eddelbuettel.com/blog/2011/04/23/) I get an error message. Specifically, the R code I was taking from the above example is >> >>

Re: [Rd] Possible bug in 'new()' for Reference Classes

2011-12-07 Thread John Chambers
Right, thanks for the catch. Actually, field names "s", "se", "sel" would also produce the bug. Partial matching of argument names bites again. This should be fixed in r-devel and 2.14 patched, as of SVN rev. 57842. Do try to follow the API in the documentation and use generator objects fo

Re: [Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread Joris Meys
2011/12/7 Barry Rowlingson : > 2011/12/7 Joris Meys : >> @Barry : regardless of whether '_' comes before or after '1' , it >> should be consistent. Adding an 'a' shouldn't shift '_' from before >> '1' to between '1' and '2', that's clearly an error. The help files >> are not stating anything about

Re: [Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread Barry Rowlingson
2011/12/7 Joris Meys : > @Barry : regardless of whether '_' comes before or after '1' , it > should be consistent. Adding an 'a' shouldn't shift '_' from before > '1' to between '1' and '2', that's clearly an error. The help files > are not stating anything about that. That's an assumption. The h

Re: [Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread peter dalgaard
On Dec 7, 2011, at 15:48 , Joris Meys wrote: > @Barry : regardless of whether '_' comes before or after '1' , it > should be consistent. Adding an 'a' shouldn't shift '_' from before > '1' to between '1' and '2', that's clearly an error. The help files > are not stating anything about that. The o

Re: [Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread Roebuck,Paul L
Do this first and try again. R> Sys.setlocale("LC_COLLATE", "C") On 12/7/11 3:41 AM, "Hervé Pagès" wrote: > Hi, > > This looks OK: > >> x <- c("_1_", "1_9", "2_9") >> rank(x) > [1] 1 2 3 > > But this does not: > >> xa <- paste(x, "a", sep="") >> xa > [1] "_1_a" "1_9a" "2_9a" >> rank(xa) >

[Rd] Possible bug in 'new()' for Reference Classes

2011-12-07 Thread Janko Thyson
Dear list, I think I stumbled across a little bug with respect to the standard initialization routine for Reference Classes. It seems that a field 'self' is treated as if it's name would be '.self' (which we know is reserved for the self reference of the instantiated object itself) and thus

Re: [Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread Gabriel Becker
I'm not an expert on Locales but those that are getting this behavior and those that aren't appear to be different. (in fact, all three sets are slightly different). Isn't sorting order based on Locale rather than any internal R code anyway? ~G On Wed, Dec 7, 2011 at 7:06 AM, Rainer M Krug wrot

Re: [Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/12/11 15:48, Joris Meys wrote: > @Barry : regardless of whether '_' comes before or after '1' , it > should be consistent. Adding an 'a' shouldn't shift '_' from > before '1' to between '1' and '2', that's clearly an error. The > help files are

Re: [Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread Joris Meys
@Barry : regardless of whether '_' comes before or after '1' , it should be consistent. Adding an 'a' shouldn't shift '_' from before '1' to between '1' and '2', that's clearly an error. The help files are not stating anything about that. The only thing I can imagine, is that '_' gets ignored (in t

Re: [Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread Barry Rowlingson
2011/12/7 Hervé Pagès : > rank(xa) See help(Comparison), specifically: "Beware of making _any_ assumptions about the collation order" followed by "Collation of non-letters (spaces, punctuation signs, hyphens, fractions and so on) is even more problematic." Barry _

[Rd] bug in rank(), order(), is.unsorted() on character vector

2011-12-07 Thread Hervé Pagès
Hi, This looks OK: > x <- c("_1_", "1_9", "2_9") > rank(x) [1] 1 2 3 But this does not: > xa <- paste(x, "a", sep="") > xa [1] "_1_a" "1_9a" "2_9a" > rank(xa) [1] 2 1 3 Cheers, H. > sessionInfo() R version 2.14.0 (2011-10-31) Platform: x86_64-unknown-linux-gnu (64-bit) locale: [1] LC_CTYPE

Re: [Rd] Unable to collate and parse R files with R CMD check

2011-12-07 Thread Uwe Ligges
On 06.12.2011 20:05, Sumukh Sathnur wrote: Hi all, I'm trying to build a package on Windows 7 (64 bit) and although R cmd build worked fine and I got pkg.tar.gz with no errors, but when I tried doing R CMD check everything turns out ok except for the warning: "checking whether package 'pkg' c

[Rd] Graphics device hook to manipulate plotmath

2011-12-07 Thread Zack Weinberg
Is there a hook that allows a graphics device to apply transformations to plotmath expressions *before* they are rendered? If there isn't one yet, would it be feasible to add one? The motivation for this hook is graphic devices that feed into something that already has support for math layout, su

[Rd] Unable to collate and parse R files with R CMD check

2011-12-07 Thread Sumukh Sathnur
Hi all, I'm trying to build a package on Windows 7 (64 bit) and although R cmd build worked fine and I got pkg.tar.gz with no errors, but when I tried doing R CMD check everything turns out ok except for the warning: "checking whether package 'pkg' can be installed ... ERROR. Installation failed.

Re: [Rd] warning for inefficiently compressed datasets

2011-12-07 Thread Uwe Ligges
On 06.12.2011 23:28, Hervé Pagès wrote: Hi, Recently added to doc/NEWS.Rd: 'R CMD check' now gives a warning rather than a note if it finds inefficiently compressed datasets. With 'bzip2' and 'xz' compression having been available since R 2.10.0, there is no excuse for not using them. Why is