similar to: Writing R-extensions

Hi, I am facing with a strange behaviour of isClass and extends when these are called in .onLoad in both R 2.12.1 and R 2.13.0. This is preventing my package from doing some object initializations at a proper place (i.e. in .onLoad). Suppose one defines two S4 classes in a package, and that one needs to check the inheritance between these two when loading the package (e.g. to validate slots

From: Prof Brian Ripley > > On Thu, 13 Apr 2006, Peter Ruckdeschel wrote: > > > Hi R-devels, > > > > in "Writing R extensions" as well as in the help > > to .onAttach(), you mention that one could > > use this function to issue a start-up message/banner > > for the package. > > > > My little wish for Easter: > > > > a

Dear all, My apologies for re-posting this question, but I have not found any solution to my problem so far. I also think that my post may have been overseen due to the posting time and high traffic on this list. I experience a problem in implementing a S4 class in a package and would appreciate your help in this matter. The class is implemented using Rcpp, which works well. I then extend

Have a question about the following NOTEs appearing on CRAN checks: > .onLoad calls: > require(methods) > > Package startup functions should not change the search path. > See section ?Good practice? in ?.onAttach. For years, I have had the following in my S4-requiring packages. ##--------------------------------------------------------------------- .onLoad <-

Hello, (Dear Richard, I hope you don't mind being Cc:'d on this thread in R-devel. This is one of the ways we can prevent similar problems from happening in the future.) Sometimes, package authors who use both exportPattern('.') and utils::globalVariables(...) get confusing WARNINGs about undocumented exports: https://stat.ethz.ch/pipermail/r-package-devel/2024q1/010531.html I

> Packages without explicit ?NAMESPACE? files will have a default one created at build or INSTALL time, > so all packages will have namespaces. A consequence of this is that ?.First.lib? functions need to be > renamed, usually as ?.onLoad? but sometimes as ?.onAttach?. Couldn't R simply regard .First.lib as the appropriate function to save many packages from being needlessly changed?

Documentation on how to put classes and methods in packages with namespace? How should I define my classes and methods in "dynamicGraph"??? (That is - Can some one point me to the documentation on how to put classes and methods in packages with a namespace? ) Currently it is done by the code below. This gives problems, when a workspace with a "dynmaicGraph" is

Hi R-devels, in "Writing R extensions" as well as in the help to .onAttach(), you mention that one could use this function to issue a start-up message/banner for the package. My little wish for Easter: a 'quietly'-type argument for .onAttach() / .First.lib() which is passed through by functions require() and library() respectively, and by means of which one could optionally

Dear developeRs, I have a package, pls, that implements package options. The users are supposed to use a function pls.options() to manipulate them. If a user changes the options, they are stored in .GlobalEnv. I was recently informed that this is against current CRAN submission policies, so I need to change that. I have looked at several different packages that implement package options, and

After building and installing R-devel from 21/07/2011 on FreeBSD 9.0-CURRENT (amd64), starting R gives the following warning: [..snip..] Beim Start - Warnmeldung: package 'datasets' in options("defaultPackages") was not found This happens with all versions after 14/07/2011. I think it is related to NEWS Sat, 16 Jul 2011 CHANGES IN R-devel PACKAGE INSTALLATION Packages without

I think you can already do this via .First(). If you start your .First with something like this [give or take some parentheses] if( !is.null( runfirst <- Sys.getenv( 'RUNFIRST'))) try( eval( parse( text=runfirst)))) then whatever you pass in as RUNFIRST=... should get executed on startup. Could even be a call to source(...) if you want to source a particular file. I have a similar

for the moment, I'm using: .onAttach <- function(libname, pkgname) { .bbg.db.conn <<- dbConnect(dbDriver("PostgreSQL"), user="blah","blah") } .onUnload <- function(libpath) { dbDisconnect(.bbg.db.conn) } which results in a hidden global variable in the global environment. I would prefer to make the assignment only in the package namespace.

Hi, I have asked this question before, but the solution I ended up with (see below) creates a note when running R CMD check. So I am trying again... I am developing a package B that, among other things, also offers some extra S3-methods for functions in package A if the user has installed A. I do not want to list A under Depends of B, as the dependency list of A is rather long, and most

I want to load an in-house library 'differently' in a particular context and, to achieve this, would like to govern the behaviour of its .onLoad() function. In a related context, Frank Harrell and I have been wondering on and off about how to tell Hmisc to be less verbose in certain situations. He achieves this by placing information in a custom field in options(). I could do the same

I am considering a package with a namespace (Rgraphviz from Bioc). I essentially want to have some error handling for loading the dll, something like wrapping it into tryCatch or similar (reason: see below). Right now I am loading the dynamic libraries by useDynLib in my NAMESPACE file. When I look at the code from loadNamespace, I have the impression that what I want is impossible

Hi guys, This probably isn't news, but when a package is given an autogenerated namespace, its .First.lib, if any, is no longer called. This causes problems, e.g., when a package is loading a dynamic library. Probably no good solution here. The initialization routines could be made to call .First.lib, code could be rewritten on the fly, a useDynlib() could be added for a package that has one,

I'm currently working on a new package for R that interfaces with an API. Most of the package's functionality requires users to supply an access key that allows the package to work with the API. I want to display text immediately upon loading the package that instructs/reminds users to enter their access key before attempting to do anything (as the package won't really work without

Hi, I wonder whether a package with namespace & dynamic library can be installed with the version number attached, ie. with the argument --with-package-versions. Is this currently possible? Using R 1.9.1 on Debian 3.0 I encounter a problem when trying to load a package installed with R91 CMD INSTALL --with-package-versions -l /mnt/local/R/R-1.9.x-libs-EpiR RIO in R started with R91

I am attempting to build a package on r-forge and running into a weird error. I have been in correspondence with the R-forge admins and am turning to r-devel on the remote chance that someone might have a guess as to what is going wrong or a suggestion about further diagnostics/experiments I could try ... The package seems to build fine on my system(s) with R CMD build --compact-vignettes

Hello to the list Some days ago, I placed a question on this maling-list and received an answer from Martin that I tried to follow. Unfortunately, I am still puzzled by the next step. I spent the whole Week-end in gathering information from the net. Some of them are almost contridtcory and I lack a good document to help me. So my first question would beL Is there a convenient document which