What exactly is the purported bug here? It seems to me that the cuts
are correct and the behaiour is as documented, but that you were not
expecting empty levels. If that bothers you, use
cut(x, breaks= "quarter")[,drop=TRUE]
On Mon, 21 Dec 2009, shmu...@googlemail.com wrote:
Full_Name: Qi
Full_Name: Mario Luoni
Version: 2.10.0
OS: Windows XP HE SP3
Submission from: (NULL) (217.194.59.134)
This piece of code:
zzz1 <- as.POSIXct("1999-03-18", tz="CET")
zzz2 <- as.POSIXlt("1999-03-18", tz="CET")
zzz1 == zzz2
as.Date(zzz1)
as.Date(zzz2)
yields TRUE for "zzz1==zzz2", but the two date
On Dec 22, 2009, at 4:18 AM, Prof Brian Ripley wrote:
As the help says
The sort order for character vectors will depend on the collating
sequence of the locale in use: see ‘Comparison’.
and that ref says
Collation of
non-letters (spaces, punctuation signs, hyphens, fractions a
On Wed, Dec 23, 2009 at 12:27 AM, Dominick Samperi
wrote:
> Stavros Macrakis wrote:
>
>> That said, as a matter of courtesy and clarity, I'd think that a fork
>> should use a different name.
>>
> Yes, the point is that this is not a legal or technical matter, it is a
> matter of professional court
In my view what has happened is not much different from a situation
where I place my
name as co-author on a research paper that you have created, without
your permission,
after making a few small edits that you may not agree with. Furthermore,
if you complain
I simply present the results (at con
Rgraphviz load problems frequently involve a mismatch between the
version of graphviz installed on the user machine, compared to the
version of graphviz used to build the package.
Rgraphviz has a name space with useDynLib(Rgrahpviz), and an .onLoad
function that checks that the versions of the ins
Good afternoon,
While I don't know the history of this particular conflict - to me the
entire *purpose* of the GPL is to ALLOW forking of code which must
remain in public. If somebody forks code and makes any change
whatsoever and then distributes either the diff or the entire previous
project, t
Dear all,
I have written a small set of functions for drawing graphical representations
of R objects and evaluations of R expressions.
It is mainly intended for pedagogical purposes. Here are some samples:
http://panini.u-paris10.fr/~sloiseau/sampleGraphics.pdf
The idea is to use some graphica
The central purpose of the GPL license is precisely to allow and indeed
encourage the behavior your are criticizing. In particular, when you
release software under the GPL, you are *explicitly* giving recipients of
the software the right to modify it pretty much in any way (trivial or
radical) the
I guess one problem is who is in charge of the name Rcpp on CRAN. For
instance, can I "fork" of yet another version of Rcpp (or any other
CRAN package) and submit it to CRAN? Can the original author submit a
completely different Rcpp package breaking all the additions made by
the new contributors
One critical aspect to this is the fact that RcppTemplate seems to
have been where the Rcpp work moved to _before_ abandoning the Rcpp
project.
http://cran.r-project.org/src/contrib/Archive/RcppTemplate/
So the 'namespace' of Rcpp was left with seemingly no public intention
of picking it up.
One
Very nice. Certainly it would be welcome to see this packaged for
widespread use.
On Wed, Dec 23, 2009 at 2:20 PM, Sylvain Loiseau
wrote:
> Dear all,
>
> I have written a small set of functions for drawing graphical representations
> of R objects and evaluations of R expressions.
>
> It is main
Nice idea.
But I think "visualR" or "seeR" are way too vague.
How about "drawExpressions", or "showExpressions"?
-Felix
2009/12/24 Sylvain Loiseau :
> Dear all,
>
> I have written a small set of functions for drawing graphical representations
> of R objects and evaluations of R expressions.
>
>
or ExpressionBlocks
On Wed, Dec 23, 2009 at 5:12 PM, Felix Andrews wrote:
> Nice idea.
> But I think "visualR" or "seeR" are way too vague.
> How about "drawExpressions", or "showExpressions"?
>
> -Felix
>
> 2009/12/24 Sylvain Loiseau :
>> Dear all,
>>
>> I have written a small set of functions f
In a previous email, i suggested two patches A and B to choose(n, k), which
solve some of its problems, but keep some of the inaccuracies of the original
implementation. I would like to suggest another patch, which i will call C
(patch-C.txt in an attachment), which eliminates the warnings obtained
Working with a number of scripts (text files with R commands) that I
"source" into R sessions from time to time.
The source() command is most convenient (at least for me)
if it only loads function definitions, and doesn't otherwise change the
interactive environment. For example, I might hav
On 23/12/2009 7:04 PM, ghe...@mathnmaps.com wrote:
Working with a number of scripts (text files with R commands) that I
"source" into R sessions from time to time.
The source() command is most convenient (at least for me)
if it only loads function definitions, and doesn't otherwise change th
This sources the indicated file into the local environment (i.e. the
environment within src) and then only copies out the objects that are
functions into the workspace so that you are only left with them.
src <- function(file) {
source(file, local = TRUE)
for(nm in ls(all = TRUE)) if (is.fun
Jeff Ryan wrote:
One critical aspect to this is the fact that RcppTemplate seems to
have been where the Rcpp work moved to _before_ abandoning the Rcpp
project.
The Rcpp package was not abandoned, it was renamed to RcppTemplate
because I thought it would be more useful for the R community to
19 matches
Mail list logo
