Sorry Dirk, I don't remember discussing this topic or alternatives with you
at all.
Have a nice day.
On Tue, 30 Jun 2020, 14:42 Morgan Morgan, wrote:
> Thanks Jan and Tomas for the feedback.
> Answer from Jan is what I am looking for.
> Maybe I am not looking in the right place buy it is not
Hello, everyone,
thank you for your quick and helpful responses and the detailed information.
Sorry for not providing a reproducible example for the (potential) bug in
`tools::makeLazyLoadDB`. The main point of my mail was the surprising
behaviour of `basename` and `dirname`. Fixing those
Hello,
We will be performing some updates on the single package builder for new
submissions today June 30. There will be a period of downtime while we run the
updates. During this time packages on the tracker will not receive automatic
builds. We apologize for any inconvenience and
On 30 June 2020 at 14:42, Morgan Morgan wrote:
| Thanks Jan and Tomas for the feedback.
| Answer from Jan is what I am looking for.
| Maybe I am not looking in the right place buy it is not easy to understand
| how these LCONS, CONS, SETCDR...etc works.
a) There are alternatives, and if memory
Thanks Jan and Tomas for the feedback.
Answer from Jan is what I am looking for.
Maybe I am not looking in the right place buy it is not easy to understand
how these LCONS, CONS, SETCDR...etc works.
Thank you
Best regards
Morgan
On Tue, 30 Jun 2020, 12:36 Tomas Kalibera, wrote:
> On 6/30/20
Thanks. Fixed in R-devel in r78754. This was related to a fix for
PR#17809, not the change to unique.default.
Best,
luke
On Tue, 30 Jun 2020, Jan Gorecki wrote:
No packages are being loaded, or even installed.
Did you try running the example on R-devel built with flags I have
provided in
On 6/30/20 1:06 PM, Jan Gorecki wrote:
It is quite known that R documentation on R C api could be improved...
Please see "5.11 Evaluating R expressions from C" from "Writing R
Extensions"
Best
Tomas
Still R-package-devel mailing list should be preferred for this kind
of questions.
Not
It is quite known that R documentation on R C api could be improved...
Still R-package-devel mailing list should be preferred for this kind
of questions.
Not sure if that is the best way, but works.
call_to_sum <- inline::cfunction(
language = "C",
sig = c(x = "SEXP"), body = "
SEXP e =
> Jan Gorecki
> on Tue, 30 Jun 2020 11:29:24 +0100 writes:
> No packages are being loaded, or even installed.
> Did you try running the example on R-devel built with flags I have
> provided in this email?
> I checked now and it is required to use
No packages are being loaded, or even installed.
Did you try running the example on R-devel built with flags I have
provided in this email?
I checked now and it is required to use --enable-strict-barrier to
reproduce the issue.
On Tue, Jun 30, 2020 at 9:02 AM Martin Maechler
wrote:
>
> >
On 6/30/20 11:48 AM, Göran Broström wrote:
On 2020-06-30 01:07, Jeff Newmiller wrote:
Your choice. Do you want to support people using older versions of R,
or not?
Is that all? No point at all with version 3 in packages? Why was it
introduced? I have seen an argument for version 2: "...
On 2020-06-30 11:58, Ivan Krylov wrote:
On Tue, 30 Jun 2020 11:48:29 +0200
Göran Broström wrote:
No point at all with version 3 in packages?
Format version 3 [1] introduces support for ALTREP objects [2].
Examples of where ALTREP might be useful include really long integer
vectors, like
On Tue, Jun 30, 2020 at 1:32 PM Martin Maechler
wrote:
>
> > Kurt Hornik
> > on Tue, 30 Jun 2020 06:20:57 +0200 writes:
>
> > Jan Gorecki writes:
> >> Thank you both, You are absolutely correct that example
> >> should be minimal, so here it is.
>
> >> l =
On Tue, 30 Jun 2020 11:48:29 +0200
Göran Broström wrote:
> No point at all with version 3 in packages?
Format version 3 [1] introduces support for ALTREP objects [2].
Examples of where ALTREP might be useful include really long integer
vectors, like 1:1e10.
--
Best regards,
Ivan
[1]
On 2020-06-30 01:07, Jeff Newmiller wrote:
Your choice. Do you want to support people using older versions of R, or not?
Is that all? No point at all with version 3 in packages? Why was it
introduced? I have seen an argument for version 2: "... needed ... to
support name spaces", but
Hi All,
I was reading the R extension manual section 5.11 ( Evaluating R expression
from C) and I tried to build a simple call to the sum function. Please see
below.
call_to_sum <- inline::cfunction(
language = "C",
sig = c(x = "SEXP"), body = "
SEXP e = PROTECT(lang2(install(\"sum\"), x));
On Mon, 29 Jun 2020 22:55:02 +0200
Göran Broström wrote:
> After googling for a while (found nothing relevant in 'WRE'), I
> understand that I have two options: (i) Change 'Depends' in
> DESCRIPTION as suggested, and (ii) using save with 'version = 2' for
> the new files.
One of the steps
> Kurt Hornik
> on Tue, 30 Jun 2020 06:20:57 +0200 writes:
> Jan Gorecki writes:
>> Thank you both, You are absolutely correct that example
>> should be minimal, so here it is.
>> l = list(a=new.env(), b=new.env()) unique(l)
>> Just for completeness, env_list
On 6/29/20 4:39 PM, Johannes Rauh wrote:
Dear R Developers,
I noticed that `basename` and `dirname` always return "UTF-8" on Windows
(tested with R-4.0.0 and R-3.6.3):
p <- "Föö/Bär"
Encoding(p)
[1] "latin1"
Encoding(dirname(p))
[1] "UTF-8"
Encoding(basename(p))
[1] "UTF-8"
Is this on
19 matches
Mail list logo