Which is not necessarily bad news. :)
I wonder if this was intended, because I did not find anything about
it in the news file. It also breaks a couple of R packages, e.g. desc,
probably more.
Is this intended?
Thanks!
This is R-devel from yesterday:
> x <- "\xfc"
> Encoding(x) <- "latin1"
>
Dear Duncan,
.Rbuildignore is spelled correctly, and no non-ASCII characters in.
All tools:::inRbuildignore(list.files(), ".") were FALSE, so I decided to
rewrite .Rbuildignore from scratch, just in case there was any extra space.
I think that was the problem because now
Dear Jeff,
I am aware I don't need to be worried about those two warnings but many
thanks anyway.
Jose Barrera
Statistician, Associate Lecturer
*IS**Global*
Barcelona Institute for Global Health - Campus MAR
Barcelona Biomedical Research Park (PRBB) (Room Hypatia)
Doctor Aiguader, 88
08003
Hi,
I am converting a couple of functions into a R-package. Many of the
functions use data.table.
I have two questions using data.table in my own package.
Normally I would put each question in separate emails but I think they
might be connected.
First question is short and I think the
On 05/03/2021 8:27 a.m., Martin Møller Skarbiniks Pedersen wrote:
Hi,
I am converting a couple of functions into a R-package. Many of the
functions use data.table.
I have two questions using data.table in my own package.
Normally I would put each question in separate emails but I think
Question one is a matter of personal preference. I personally stick to
explicitly state a double column depency with data.table.
Question two. Just replacing the dot by list is sufficient AFAIK.
Hope this helps
Le ven. 5 mars 2021 à 14:28, Martin Møller Skarbiniks Pedersen <
Martin,
Both questions are FAQs. Searches at e.g. StackOverflow might have lead you
to a solution (and you can search there, key is to add the tag i.e. make [r]
or [data.table] part of the search term).
The first one is a generic package programming question. You can use Imports:
in
Thank you. Glad to hear it's useful.
This plain TeX/LaTeX vignette engine is implemented using base R. If
someone is willing to drive the efforts, I think it's not too much
work to refactor it and propose it for base R itself, where I think it
belongs, e.g. in the 'utils' package where Sweave
On 05/03/2021 2:40 p.m., Henrik Bengtsson wrote:
Thank you. Glad to hear it's useful.
This plain TeX/LaTeX vignette engine is implemented using base R. If
someone is willing to drive the efforts, I think it's not too much
work to refactor it and propose it for base R itself, where I think it
I would like to test for NaN inside C++ code that lives inside a CRAN
package.
Following the StackOverflow question linked below, I was using
#define isNAN(a) (a!=a)
which I *think* used to work, but at some point along the way it stopped
working due to compiler/flag changes. I'm thinking
Thanks! Now I see this is in Writing R Extensions, should have
looked more carefully ...
On 3/5/21 9:00 PM, Andrew Simmons wrote:
Hello,
You probably want one of the following
ISNA TRUE for R's NA only
ISNAN TRUE for R's and IEEE's NaN
R_IsNaN TRUE for IEEE'S NaN only
On
Hi bioc-devel,
My package contains a function that requires Cytoscape.
For this function to run, I need to have Cytoscape installed and open on my
computer.
https://github.com/rosscm/fedup/blob/main/R/femap.R
This poses an issue when attempting to test the function since I can’t control
Hi Catherine,
If I recall correctly, the builders are headless (i.e. they don't
have displays attached), and Cytoscape does require a display to run.
Anything in my vignette that required Cytoscape I cached the images and
then inserted them into the vignette, I think I had a function that would
Dear bioconductor team,
Recently, I want to upgrade our package EnMCB and add some functions.
However, the functions are based on a GitHub package ("Coxboost")
This package has been removed from CRAN, but I can find it on GitHub(
https://github.com/binderh/CoxBoost)
Therefore, can I depend on
14 matches
Mail list logo
