similar to: Roxygen2: version 2.2

This is an error message from R. For example, if you give the following R commands > a <- 5 > a$foo This will generate the error message: Error in a$foo : $ operator is invalid for atomic vectors So you can search for the string 'x$tag' in your code (or possibly in the package). HTH, Eric On Wed, Jan 17, 2018 at 3:16 PM, Martin M?ller Skarbiniks Pedersen < traxplayer at

If a package has importClassesFrom(P, C) in its NAMESPACE, then should it _also_ have importClassesFrom(P, <superclasses of C exported from P>) importClassesFrom(Q, <superclasses of C exported from Q>) ## and so on ... ? I think that WRE could be more clear on this point, and in any case I _think_ that the answer is yes. Notably, I think that this rule would

Hi, I am trying to create my first R package. I will later today put the files on Github. However I gets this error and I can't find any reason for it: R> roxygen2::roxygenise() First time using roxygen2. Upgrading automatically... Error in x$tag : $ operator is invalid for atomic vectors R> Any ideas? Regards Martin M. S. Pedersen [[alternative HTML version deleted]]

If a package defined an S3 generic and an S4 generic for the same function (so as to add methods for S4 classes to the existing code), how do I set up the namespace to have them exported? With import(stats) exportMethods(bigglm) importClassesFrom(DBI) useDynLib(biglm) export(biglm) export(bigglm) in NAMESPACE, the S3 generic is not exported. > methods("bigglm") [1] bigglm.RODBC*

Dear colleagues, preparing a release of my package ?polmineR? I encountered the following issue with a new warning issued when running R CMD check with the --as-cran option on Debian with R-devel. To reexport the magrittr pipe operator %>%, my package adopted I snippet you?d see in the dplyr package, for instance: #' @importFrom magrittr %>% #' @export magrittr::`%>%` The

Hadley Wickham refactored roxygen, making it more maintainable and robust; the changes are so significant that we decided to nominate it roxygen2: http://cran.r-project.org/web/packages/roxygen2/index.html Some highlights: * it's faster; * usage has been improved (the @usage tag should be obsolete); * @rdname merges documentation for multiple functions into one file. For details,

Hadley Wickham refactored roxygen, making it more maintainable and robust; the changes are so significant that we decided to nominate it roxygen2: http://cran.r-project.org/web/packages/roxygen2/index.html Some highlights: * it's faster; * usage has been improved (the @usage tag should be obsolete); * @rdname merges documentation for multiple functions into one file. For details,

Hi all, I'm trying to come to grips with how to document S4 methods using ROxygen - mostly following posts such as this: http://tinyurl.com/ae3kdno I just can't get it to work (this is roxygen2_2.2.2). I attach an example below which seems parsed properly, but "R CMD check" keeps complaining > ... > Undocumented S4 methods: > ... > generic 'set<-' and

Hello: I recently submitted a package to R using devtools:release(). I received no errors, warnings, or notes in R CMD check. However, I received two notes in devtools::release(): 1) checking CRAN incoming feasibility ... NOTE 2) checking package dependencies ... NOTE No repository set, so cyclic dependency check skipped After I submitted the package, I was told to fix two things, of which

FYI, I plan on implementing this for F31 if no issues arise. ---------- Forwarded message --------- From: Ben Cotton <bcotton at redhat.com> Date: Tue, 2 Jul 2019 at 10:55 Subject: Fedora 31 System-Wide change proposal: Automatic R runtime dependencies To: <devel-announce at lists.fedoraproject.org>, Development discussions related to Fedora <devel at lists.fedoraproject.org>

Hello! I am truing to compile an R-package having c-code. I put foo.c in src/ folder and useDynLib("foo") in NAMESPACE file. When trying R CMD check, I got an error message that shared object 'foo' is not found. Then I did R CMD SHLIB foo.c first. However, after that, I got warnings from R CMD check that there is an object file in /src folder. Even worse is if I run R CMD

On 17 January 2018 at 14:30, Eric Berger <ericjberger at gmail.com> wrote: > This is an error message from R. > For example, if you give the following R commands > > a <- 5 > > a$foo > This will generate the error message: > Error in a$foo : $ operator is invalid for atomic vectors > > So you can search for the string 'x$tag' in your code (or

I have a source file with oxygen-style comments (and description & licence files), and I?m trying to build a package. oxygen & devtools seem to work, and the tarball exists, but install.packages balks. Does anyone know what?s happening? Regards, Jorgen Harmse. > roxygenise(package.dir,clean=TRUE) Setting `RoxygenNote` to "7.3.1" ? roxygen2 requires "Encoding:

Dear R devels, let's say I have three packages "pkg1", "pkg2" and "pkg3" which all contain new S4 classes and methods. Where "pkg3" depends on "pkg2" and "pkg2" depends on "pkg1". Moreover, all three packages have namespaces. 1) I use ".onLoad <- function(lib, pkg) require(methods)". Do I also have to

Hi, I've seen that some packages use .packageName internally to infer their own name. Is that officially supported? I could not find it documented anywhere. There's utils::packageName(), which internally looks for .packageName. However, if the latter is not found, it may return NULL whereas an error would be more appropriate if a package name is expected. Using .packageName would give

Hi, i want to use Puppet to install all packages from a webserver (no repository) . Therefore I wrote following Script: class install_package { case "$operatingsystem" { SLES: { notify {"${operatingsystem} ${operatingsystemrelease} detected":} notify {"Installing $packagename now:":}

The current version of the methods package now has a namespace. Packages using S4 methods and classes can have NAMESPACE files. New directives can be included in NAMESPACE files to import and export classes and methods. Namespaces allow cleaner definition of the API for packages, and are needed for future improvements to R. NOTE: This is a major revision. In principle, it should be back

I was building a package that uses the new generic @ and kept having errors with ?roxygen2? documentation. ?roxygen2? generated NAMESPACE added `@.newclass` as a newly exported function, not as a S3method. At first I thought this must be a bug in roxygen2 and they lag behind the new developments in R. But after some investigation I found that ?roxygen2? is using tools:::.get_internal_S3_generis()

This issue might go deeper - I was not successful in passing R CMD checks for the usage files. R CMD check kept showing errors for `@` declarations, even thou they were identical to `$` declarations (which passed fine). Seems like the usage check functions are not prepared for `@` - also in tools:::.S3_method_markup_regexp > On Apr 28, 2023, at 10:34 PM, Karolis Koncevi?ius

Dear Duncan, With all respect, but I strongly disagree on your stance regarding roxygen2 for multiple reasons: 1. It is in my humble opinion not correct to evaluate a tool based on the abuse of some users. It's not because people write packages with bad documentation, that roxygen2 is to blame. I use roxygen2, and I care a great deal about documentation. So I actually took a bit offense