similar to: loadNamespace and versionChecking and the otherpackage::otherfun syntax

On 26/11/2014, 7:38 PM, Geoff Lee wrote: > Many thanks Duncan for the quick response. A little too quick, it seems... > > A bug is a relief in a way. I've been digging my way deeper into this (and > learning more as I go) for several days now - but it is a diversion from (a > diversion from) my main goal :-( > > Is there somewhere specific I should report or log the

On 26/11/2014, 8:29 PM, Geoff Lee wrote: > Hi Duncan > > The difference is that in your call to loadNamespace, the versionCheck list > has 3 components (name, op and version), whereas the documentation only > mentions 2 (op and version). > loadNamespace 'works' for me provided I add a third component to the list > (even a nonsense one). > > What I haven't

Hi Duncan, Many thanks (yet again). With the hint given by your earlier email (viz that currently loadNamespace expects a 3rd component called name in the list that is used for the versionCheck argument) I had another look at what was going on with my toy examples yesterday evening. I'm still working on my issue, but thus far I have: 1) Confirmed that internal calls to loadNamespace

Summary: I think you've found a bug. On 26/11/2014, 5:39 PM, Geoff Lee wrote: > Hi > > > > I'm still exploring the R programming universe, so if this is being asked in > the wrong place, or in the wrong way (e.g. too verbose or lacking in crucial > detail or in the wrong format) please let me know > > > > I am trying to understand when the version

Dear all, When creating new functions in a package, there is a "See also" component in the Rd file. Usually one uses \link{otherfun}, if the other function is from the same package, or \link[otherpackage]{otherfun} otherwise. The trouble is that I install new packages not in the default R library folder, but into some other subfolder in my home, so the link searches for

Many thanks Duncan for the quick response. A bug is a relief in a way. I've been digging my way deeper into this (and learning more as I go) for several days now - but it is a diversion from (a diversion from) my main goal :-( Is there somewhere specific I should report or log the bug or will that happen from this mailing-list automatically? (I have seen the Bug Tracking link on the

Hi Duncan The difference is that in your call to loadNamespace, the versionCheck list has 3 components (name, op and version), whereas the documentation only mentions 2 (op and version). loadNamespace 'works' for me provided I add a third component to the list (even a nonsense one). What I haven't yet had the fortitude to do is track down through the code to see what the arguments

Hi I'm still exploring the R programming universe, so if this is being asked in the wrong place, or in the wrong way (e.g. too verbose or lacking in crucial detail or in the wrong format) please let me know I am trying to understand when the version constraints for packages which appear in the Imports field of a DESCRIPTION file are checked. Along the way I've hit a snag

Hi, in (at least) R v2.14.2 and R v2.15.0 alpha, '.conflicts.OK' is not exported and hence to seen by library(). DETAILS: In R-devel thread '[Rd] Suggestion: Not having to export .conflicts.OK in name spaces' on Mar 17-22, 2010 [https://stat.ethz.ch/pipermail/r-devel/2010-March/057017.html] it was discussed that one had to export '.conflicts.OK' in the namespace,

Dear R-users, I am having some issues with a package I am working on (using R 2.12.1 in a Linux environment) and would like to have your opinions/advises. My package - let's call it mypackage for the purpose of this email - passes all checks of R CMD check, except for the following failure message: Error : .onLoad failed in loadNamespace() for 'mypackage', details: call:

>>>>> Laurent Gautier >>>>> on Sun, 15 Sep 2019 15:01:09 -0400 writes: > In case a search engine leads someone with the same issue > here, I am documenting the point I reached: > I can reproduce the issue with a small example when > forcing R to not load any package at startup time (using > an Renviron file): ``` package <-

hi, i'm having some trouble getting a package to load a shared library object in .onLoad(...) i have a shared object file, say "mylib.so". if i start an R session, and via the CLI specify the actual library via: > dyn.load("mylib.so") everything works quite well (i.e. i can then follow with some .Call (...) methods) now, i'd like to include this shared library in

> On Dec 7, 2017, at 10:47 AM, James Henson <jfhenson1 at gmail.com> wrote: > > Hello R Community, > > I inadvertently updated packages via R Studio when a package was open. Now > when R Studio is opened the message below appears in the console panel. > > Error in loadNamespace(name) : there is no package called ?yaml? > > Error in loadNamespace(name) :

Hi, I get an error from loadNamespace in the following situation (on R-2.15.3, R-devel 2013-03-26 r62409, and fresh R-3.0.0): - package A has an optional (suggests) dependency to package C, which is tested at load time in .onLoad, via require(). - package B depends on package A, which is loaded when B is lazy-loaded at install time. - package B is installed with package C installed If one now

>>>>> Thomas Lin Pedersen <thomasp85 at gmail.com> >>>>> on Mon, 22 Jan 2018 14:32:27 +0100 writes: > Hi I?ve just spend a bit of time debugging an error > arising in `loadNamespace`. The bottom line is that the > `vI` object is assigned within an `if` block but expected > to exist for all of the remaining code. In some cases

My advice would be to avoid the network in one of the following ways 1. Store installed packages on your local drive 2. Copy the installed packages to a tempdir on your local drive each time the script is executed 3. Keep an R session running in perpetuity and source the scripts within that everlasting session 4. Rewrite your scripts to use base R only. I suspect this solution list is

It's possible to run R (or a c parent process) as a background process via a named pipe, and then write script files to the named pipe. However, the details depend on what shell you use. The last time I tried (which was a long time ago), I created a small c program to run R, read from the named pipe from within c, then wrote it's contents to R's standard in. It might be possible to

Hello R Community, I inadvertently updated packages via R Studio when a package was open. Now when R Studio is opened the message below appears in the console panel. Error in loadNamespace(name) : there is no package called ?yaml? Error in loadNamespace(name) : there is no package called ?yaml? When running R code, so far the only function that has not worked is datatable () in the ?DT?

When I run the following: cd \Rpkgs rcmd install mypackage -l library I get a message that it cannot find quadprog which is a library that mypackage depends on. Error: package 'quadprog' could not be loaded I previously used C:\Program Files\R\rw2011\library as my library for CRAN packages and did not have a problem but now that I use C:\Program Files\R\library this problem

Hello all, (Thank for your reply) I have a web-application in Apache Tomcat, when i start R in this application, I used packe RSJava Code ROmegahatInterpreter interp; String [] rargs = {"--no-save"}; REvaluator e; interp = new ROmegahatInterpreter ( ROmegahatInterpreter.fixArgs(rargs),false ); e =new REvaluator (); Errors ================ R version 2.10.1 (2009-12-14)