search for: neonira

...ll 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 <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? >> >...

...results will vary according to the parameter value, allowing strict compliance for new package names and lazy compliance for older ones. Doing so allows to enforce a new package name convention while also insuring continuity of compliance for already existing package names. Fabien GELINEAU alias Neonira Le ven. 9 ao?t 2019 ? 18:40, Kevin Wright <kw.stat at gmail.com> a ?crit : > Please, no. I'd also like to disallow uppercase letters in package names. > For instance, the cuteness of using a capital "R" in package names is > outweighed by the annoyance of trying to r...

...ignal in R? Though I dug up the R documentation, I haven't found any single relevant example. I could wrap C/C++ unix signal management using RCPP of course. Prior doing so, I wish to be sure that there exist no other available alternative, already implemented and tested. Let me know. Best. Neonira [[alternative HTML version deleted]]

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 ?...

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 --...

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 th...

...t analysis of case conventions in existing > CRAN package names ... I'll start. > > > a1 <- rownames(available.packages()) > > cute <- "[a-z]*R[a-z]*" > > table(grepl(cute,a1)) > > FALSE TRUE > 12565 2185 > > > On 2019-08-09 2:00 p.m., neonira Arinoem 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? > > > > This could be imple...

...of the cuteR variety. Bonus points for the first analysis of case conventions in existing CRAN package names ... I'll start. > a1 <- rownames(available.packages()) > cute <- "[a-z]*R[a-z]*" > table(grepl(cute,a1)) FALSE TRUE 12565 2185 On 2019-08-09 2:00 p.m., neonira Arinoem 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? > > This could be implemented by a single function,...

...d and distinguish-able immediately, both for humans and code parsers. Could you tell me, who should I get in touch with to share and promote this need, that I believe, could bring a new frontier to R, and could generate a lot of benefits for R users community. Best regards. Fabien GELINEAU, a.k.a Neonira [[alternative HTML version deleted]]

@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

Are there technical reasons that package names cannot be snake case? This seems to be enforced by `.standard_regexps()$valid_package_name` which currently returns "[[:alpha:]][[:alnum:].]*[[:alnum:]]" Is there any technical reason this couldn't be altered to accept `_` as well, e.g. "[[:alpha:]][[:alnum:]._]*[[:alnum:]]" I realize that historically `_` has not