similar to: Managing unix signal in R

I do not follow you Gabriel. Package name must not use digit numbers. Tarbal will use them, taken from the DESCRIPTION file, version field. That's why I consider the weird case name you presented as irrelevant, and not to be considered. Le ven. 9 ao?t 2019 ? 20:41, Gabriel Becker <gabembecker at gmail.com> a ?crit : > > > On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem

Won't it be better to have a convention that allows lowercase, dash, underscore and dot as only valid characters for new package names and keep the ancient format validation scheme for older package names? This could be implemented by a single function, taking a strictNaming_b_1 parameter which defaults to true. Easy to use, and compliance results will vary according to the parameter value,

Naming policies are always tricky. The one proposed by Hadley, as the one proposed by Google, are usable but not optimal according to most common needs, that are 1. Name a package 2. Name a class 3. Name a function 4. Name a parameter of a function 5. Name a variable My approach is the following 1. Package names should be made of lowercase characters, dash, dot and underscore 2. Class names

The Rcpp package and some related packages such as RcppArmadillo make use of (local) wrappers around the utils::package.skeleton() function for creating (basic yet functional) packages using Rcpp or RcppArmadillo. RStudio also exposes this under the graphical menu as a nice way to construct a package. But it seems that something changed quite recently in R. I looked into this a little yesterday

On 2019-08-09 14:27, neonira Arinoem wrote: > I do not follow you Gabriel. Package name must not use digit numbers. > Tarbal will use them, taken from the DESCRIPTION file, version field. > > That's why I consider the weird case name you presented as irrelevant, > and > not to be considered. ggplot2 ? Numbers are allowed in package names right now. > Le ven. 9 ao?t

Hi Neonira! The \blacktriangleright macro is defined in LaTeX package "amssymb". According to Writing R Extensions (section 2.6 Mathematics), "only basic LaTeX can be used, there being no provision to specify LaTeX style files such as the AMS extensions" (in Rd files). Best, - Mikko -----Alkuper?inen viesti----- L?hett?j?: R-devel <r-devel-bounces at r-project.org>

@steve Seek for online document named "writing R extensions" chapter 2. It tells how to describe a list structure using item markup for R documentation files, if indeed this matches your search, thing I am not sure. Something that looks like... value{ The \\code{list} owns following names \\item{alpha}{double vector} \\item{beta}{integer vector} \\item{delta}{raw vector} } Best Le

On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem <neonira at gmail.com> wrote: > Won't it be better to have a convention that allows lowercase, dash, > underscore and dot as only valid characters for new package names and keep > the ancient format validation scheme for older package names? > Validation isn't the only thing we need to do wrt package names. we also need to

Creeping code complexity ... I like to think that the cuteR names will have a Darwinian disadvantage in the long run. FWIW Hadley Wickham argues (rightly, I think) against mixed-case names: http://r-pkgs.had.co.nz/package.html#naming. I too am guilty of picking mixed-case package names in the past. Extra credit if the package name and the standard function have different cases! e.g.

Hi, I am unable to install tibble, a required package for ggplot2 in R. I am running R (version 3.3.2 ) in RStudio (version 1.0.44). My OS is ubuntu 14.04 (64 bits). I get the same error when running R from the terminal. Any help would be gretly appreciated. Kind regards, Terje **************** Error messages: **************** install.packages("tibble") Installing package into

I am running into a wall getting my system to work with rcpp and inline. Following Dirk's advice on stackoverflow, I hope someone is able to help me. My steps were to install MinGW 32 bit first, then installing Rtools, I disabled MinGW's entry in the PATH. I am trying to get the following code to work: library(Rcpp) library(inline) body <- ' NumericVector xx(x); return wrap(

Hello My colleagues asked me to install "R" with module "shiny". R version 3.0.1 compiled fine on Solaris 10 and is running well. I tried to install "shiny". With the dependencies "Rcpp" should be installed before. But the compile step did fail. See below. The initial error message is "Error in dyn.load(file, DLLpath = DLLpath, ...) :"

Hello My colleagues asked me to install "R" with module "shiny". R version 3.0.1 compiled fine on Solaris 10 and is running well. I tried to install "shiny". With the dependencies "Rcpp" should be installed before. But the compile step did fail. See below. The initial error message is "Error in dyn.load(file, DLLpath = DLLpath, ...) :" Before

On 06/06/2020 3:06 p.m., Dirk Eddelbuettel wrote: > > The Rcpp package and some related packages such as RcppArmadillo make use of > (local) wrappers around the utils::package.skeleton() function for creating > (basic yet functional) packages using Rcpp or RcppArmadillo. RStudio also > exposes this under the graphical menu as a nice way to construct a package. > > But it

Hello, I'm currently working on making Rcpp use the feature described here more: http://cran.r-project.org/doc/manuals/R-exts.html#Linking-to-native-routines-in-other-packages To give more context, Rcpp has for a long time built what we called "the Rcpp user library", i.e. a library we could link against user the linker. We were then producing appropriate linker flag with

Hi, Im not sure if this is the right place to post this. I am using Xubuntu Karmic Koala and am trying to use the Rcpp package. I am testing it using a simple code that takes in a vector and adds 1 to each element: #include <Rcpp.h> // This file takes in a vector and adds one to each entry RcppExport SEXP addone(SEXP vec){ // create a local copy of vec Rcpp::NumericVector

Hello, I have some problems to migrate to R >3.0 my devel machine (R.2.15.2). So I decided to start from scratch with a brand new virtual machine. Downloaded latest network install of debian testing, not stable (jessie/sid, SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux) installed only with ssh-server and basic utilities (no X). Then I installed R by: apt-get install

Hi, I am a newbie to Rcpp packages, and got problems in having basic set-ups for Rcpp under windows xp. Here is the list I have done. 1) installed Rtools and have no problem in compiling .c file. 2) installed Rcpp packages 3) set enviroment variables 'path' to make C:\Program Files\R\R-2.12.0\library\Rcpp\include\ searchable The sample C++ code I used is from the original website:

Hi all, it seems that from R 4.0.1 EXTPTR_PTR can be either a macro or a function, depending on whether USE_RINTERNALS is requested. Jeroen helped me find that this was in 78592: https://github.com/wch/r-source/commit/c634fec5214e73747b44d7c0e6f047fefe44667d This is a problem, because binary packages that are built on R 4.0.1 or R 4.0.2 will potentially not load on R 4.0.0, if they use the

Hello, I am trying to use Rinside package in my VC++.Net program ( using Visual Studio 8.0 environment). I have downloaded Windows binary of RInside from the following link http://cran.r-project.org/web/packages/RInside/index.htm Version of RInside - 0.2.3 While compiling the program , i am getting about 69 error. Some of them are the folllowing ones. Please me in solving the following issue