Re: [R-pkg-devel] [Rd] static html vignette

2024-01-06 Thread Jan Gorecki
I may add two cents on that as we recently made this change in data.table. Using markdown package instead of rmarkdown as a vignette engine reduced burden caused by extra dependencies tremendously. Moreover it made package to not even need c++ compiler, as knitr and markdown both (and their

[R-pkg-devel] DESCRIPTION file Imports of base R packages

2023-10-03 Thread Jan Gorecki
Hello, I noticed some packages define Imports in DESCRIPTION file listing base R packages like methods, utils, etc. My question is that if it is necessary to list those* dependencies in DESCRIPTION file, or is it enough to have them listed in NAMESPACE file? * by "those" I mean packages listed

Re: [R-pkg-devel] R_orderVector1 - algo: radix, shell, or another?

2023-09-26 Thread Jan Gorecki
Thank you Ivan for all detail. I was looking for particular algo for benchmarking purpose. On Mon, Sep 25, 2023 at 9:26 AM Ivan Krylov wrote: > В Sun, 24 Sep 2023 10:38:41 +0200 > Jan Gorecki пишет: > > > > https://github.com/wch/r-source/blob/ed51d34ec195b89462a8531b9ef30b7

Re: [R-pkg-devel] R_orderVector1 - algo: radix, shell, or another?

2023-09-24 Thread Jan Gorecki
t the R console? > > > On September 24, 2023 1:38:41 AM PDT, Jan Gorecki > wrote: > >Dear pkg developers, > > > >Are there any ways to check which sorting algorithm is being used when > >calling `order` function? Documentation at > >https://stat.ethz.ch/R-manua

[R-pkg-devel] R_orderVector1 - algo: radix, shell, or another?

2023-09-24 Thread Jan Gorecki
b72e47204/src/main/sort.c#L1133 If there is no way to check sorting algo, could anyone describe which one R_orderVector1 uses, and if there is easy API to use different ones from C? Best Regards, Jan Gorecki [[alternative HTML version deleted]] ___

[R-pkg-devel] safely allocate SEXP and handle failure

2023-09-21 Thread Jan Gorecki
it is something like that: int *x = malloc(nx*sizeof(int)); if (!x) { my_fun_to_set_exception_signal(); free(x); return; } How can I do it for creating SEXP object? Best Regards, Jan Gorecki __ R-package-devel@r-project.org mailing list https

Re: [R-pkg-devel] details of CRAN's r-devel-linux-x86_64-debian-clang

2020-10-27 Thread Jan Gorecki
(which registers generic method), because a particular unit test required xts to be present. Now I am able to reproduce the problem. On Sun, Oct 25, 2020 at 12:17 PM Jan Gorecki wrote: > > Thanks Hugh, > I must have dropped it when pasting to email. I checked again and it > does

Re: [R-pkg-devel] details of CRAN's r-devel-linux-x86_64-debian-clang

2020-10-25 Thread Jan Gorecki
ALENV_ > > not > > R_S3_METHOD_LOOKUP_BASEENV_AFTER_GLOBALENV_ > > (i.e. you seem to have dropped the initial underscore)? > > On Sun, 25 Oct 2020 at 20:01, Jan Gorecki wrote: > > > > Dear community, > > > > I am getting an error on CRAN on r-devel-linux-x86_64-debian-clang machine > > on

[R-pkg-devel] details of CRAN's r-devel-linux-x86_64-debian-clang

2020-10-25 Thread Jan Gorecki
web/checks/check_flavors.html "Details" are currently provided only for 3 machines there. Having "details" for r-devel-linux-x86_64-debian-clang would probably answer my question without involving readers of this mailing list. Best Regards, Jan Gorecki __

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-07-02 Thread Jan Gorecki
c > > Gabor > > > On Thu, Jul 2, 2020 at 10:06 AM Jan Gorecki wrote: > > > > Hi, > > What is the recommended way to test for those issues locally? > > If it is tested during cran submission, then seems reasonable to be enabled > > just by --as

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-07-02 Thread Jan Gorecki
Hi, What is the recommended way to test for those issues locally? If it is tested during cran submission, then seems reasonable to be enabled just by --as-cran switch. Is it? Thanks On Wed 17 Jun, 2020, 12:32 AM Wayne Oldford, wrote: > Thank you! > > -Original Message- > From: Gábor

Re: [R-pkg-devel] Rbuildignore a file type from a top level directory only

2020-06-21 Thread Jan Gorecki
Works great, thanks On Sun, Jun 21, 2020 at 4:21 PM Hugh Parsonage wrote: > > Perhaps > > ^[^/]+\.R$ > > On Sun, 21 Jun 2020 at 22:31, Jan Gorecki wrote: > > > > Hi R developers, > > > > What is the proper way to define an entry in .Rbuildignore file

Re: [R-pkg-devel] R_MAKEVARS_USER fail to pass down to sub-makes?

2020-06-18 Thread Jan Gorecki
tallation is > run in a temporary directory not from the directory you call `R CMD INSTALL` > from. > I observed similar behavior to what you describe when I had the MAKEVARS_USER > file as a relative path, but using an absolute path produced the expected > result. > > On M

Re: [R-pkg-devel] Forward function call

2020-06-09 Thread Jan Gorecki
"pkg::fun" cannot be a name because it is a function call already `::`(pkg, fun). On Tue, Jun 9, 2020 at 8:10 AM Martin Maechler wrote: > > > Göran Broström > > on Mon, 8 Jun 2020 23:02:30 +0200 writes: > > > Thanks for the responses! > > I found the suggestion > > >

Re: [R-pkg-devel] R_MAKEVARS_USER fail to pass down to sub-makes?

2020-06-01 Thread Jan Gorecki
ystem call on Windows... so your syntax for > setting an environment variable is not portable. > > On June 1, 2020 11:10:41 AM PDT, Jan Gorecki wrote: > >Thank you Jeff for your comments. > >Yet they does not seem to be related. > >a) Environment variable is created in

Re: [R-pkg-devel] R_MAKEVARS_USER fail to pass down to sub-makes?

2020-06-01 Thread Jan Gorecki
tem call. > > b) The syntax you have used is shell-specific, so does not look portable. > > On June 1, 2020 4:58:19 AM PDT, Jan Gorecki wrote: > >Hi package devel support, > > > >I am trying to use R_MAKEVARS_USER to customize build, rather than > >.R/Ma

[R-pkg-devel] R_MAKEVARS_USER fail to pass down to sub-makes?

2020-06-01 Thread Jan Gorecki
Hi package devel support, I am trying to use R_MAKEVARS_USER to customize build, rather than .R/Makevars. It is properly displayed from config CFLAGS but during package install it doesn't seem to work. In R-admin in "6.3.3 Customizing package compilation" there is: > Note that these mechanisms