Hi Achim
Quick Q: why do some palettes have a hyphen in the name and others not?
David
On Tue, 2 Apr 2019 at 00:38, Achim Zeileis wrote:
> Hi everyone,
>
> I wanted to draw your attention to a new post on the
> developer.R-project.org blog:
>
> https://developer.R-project.org/Blog/public/2019/
Hi David:
Quick Q: why do some palettes have a hyphen in the name and others not?
I followed the naming conventions of the respective packages that provide
the original for the the HCL-based approximations. But when you specify
the palette name in hcl.colors() all hyphens, spaces, and the
c
Hey,
Does someone have comments on the v4 of the proposed patch?
Kind regards,
Kurt
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Hi Z
I think supporting HCL color spaces more, is a *very* good idea.
However, I doubt many R users, understand the motivation for HCL color
spaces.
I've reproduced Ross Ihaka's notes on color, on my personal website:
https://sites.google.com/site/spurdlea/exts/ihaka_r_stats_787_10_color.pdf
(Th
Oops.
I didn't notice that you have references on your blog.
The more references the better, I guess.
[[alternative HTML version deleted]]
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Abs,
thanks for the feedback. As you noticed meanwhile we had linked Ross's
2003 paper as well as a few other references. The slides from Ross are a
useful addition, I didn't know these (only parts of them).
Also we didn't want to list all of the references in the blog post but
linked to the
With
f <- function(x) for (i in 1) x
fc <- cmpfun(f)
(my previous example), error message of
fc(is.numeric(y))
shows the originating call as well, while error message of
f(is.numeric(y))
doesn't. Compiled version behaves differently.
Even with
f <- function(x) for (i in 1) {x; eval(expression(i))}
