similar to: Variance generic function:

I have constructed the following functions and need a little clarification: ### function to fit the model parameters jml.fit <- function(dat, con = 1e-3, bias=FALSE, ...){ do stuff ... } ### default function which calls jml.fit jml.default <- function(dat, con = 1e-3, bias=FALSE, ...){ result <- jml.fit(dat, con = 1e-3, bias) result$call <- match.call() class(result) <-

Hi all, I am trying to package a library in R 1.6.1 (Windoze XP). I have read the document "Writing R extensions" and think I have done things correctly (though apparently not). I have searched the mail archives for help to no avail. When I try to attach the library using, eg > library( libname, lib.loc=path.to.library) I get this message: Warning message: NAs introduced by

I have a generic function test.equal <- function(obj1, obj2, ...) UseMethod("test.equal") however, the only argument that specific methods use is "fuzz" so I would like to change this to test.equal <- function(obj1, obj2, fuzz=???) UseMethod("test.equal") The problem is that some methods use slightly different default values for fuzz than others. How should

I've been putting together a package that defined generic methods for database access. The packages is called "Rdbi." It borrows as much as possible from existing database packages / proposals. I'd like to start a discussion about the proposed interface. Here's what I've come up with so far: # # Rdbi: connectionMethods.R # dbConnect <- function(dbObj, ...)

In R 1.5.0 (and earlier): > print function (x, ...) UseMethod("print") > summary function (object, ...) UseMethod("summary") Is there a reason for this inconsistency in the name of the object? It makes a single help file for both functions look ugly, because it has to document both "x" and "object", which are really the same thing. Duncan

Dear R-Users, I noticed that *read* is not a generic function. Although it could benefit from the functionality available for generic functions: read = function(file, ...) UseMethod("read") methods(read) ?# [1] read.csv???? read.csv2??? read.dcf???? read.delim read.delim2? read.DIF???? read.fortran ?# [8] read.ftable? read.fwf???? read.socket? read.table The users would still

I have posted this message on r-lang, but it is perhaps more appropriate on r-devel: --- Hello, I'm puzzled by a problem with call to diag(), rowSums(), rownames() on objects of class "dgtMatrix", created by sparseMatrix() or spMatrix(). I use Matrix 0.999375-30. The weird thing is that I don't encounter any problem when I use this functions on the R prompt, or

I'm trying to write some functions extending influence measures to multivariate linear models and also allow subsets of size m>=1 to be considered for deletion diagnostics. I'd like these to work roughly parallel to those functions for the univariate lm where only single case deletion (m=1) diagnostics are considered. Corresponding to stats::hatvalues.lm, the S3 method for class

Dear R developers, As you might have noticed, recent changes in R-dev will not allow the definition of S3 methods with S4 classes. But until now, we have defined "time<-" in our 'timeSeries' package as an S3 generic because other packages are using the same function. Indeed, if we had defined it as an S4 generic, the other packages would not coexist well with ours.

Hi, I've been using the package "graph" in the BioConductor assortment and writing some functions based on its classes. My question is not specific to this package or BioConductor (I think), but it serves as a useful example. I recently wanted to look at the code for the function "edgeMatrix" for the class "graphNEL". Usually I would type > func.foo and

Hello list. This is from an R session (admittedly, I''m still using R 2.11.1): > print function (x, ...) UseMethod("print") <environment: namespace:base> > showMethods("print") Function "print": <not a generic function> Don''t the two results contradict each other? Or do I have a terrible misunderstanding of what

On 16/12/2016 12:35 PM, Karl Millar wrote: > A couple of points: > - rebuilding dependent packages is needed if there is an ABI change, > not just an API change. For packages like Rcpp which export inline > functions or macros that might have changed, this is potentially any > change to existing functions, but for packages like Matrix, it isn't > really an issue at all

as.factor / as.ordered is not written as a generic. This differs from as.numeric, as.matrix, and other as.*. The following seems to address this and does not break make check-all. FWIW, the patch is against r55563, because with r55564 I see /home/mtmorgan/src/R-devel/src/main/dounzip.c:75:15: error: storage size of ?dt? isn?t known /home/mtmorgan/src/R-devel/src/main/dounzip.c:88:5: warning:

Hi, Following the Writing R Extensions manual, I created a method for the cor function. As cor is not a generic, I followed the advice of section 6.1 of the same manual and did the following: cor <- function(x, ...) UseMethod("cor") cor.default <- stats::cor cor.symcoca <- function{ some code } I used package.skeleton to create the basic set-up of my package, containing the

On Fri, Feb 20, 2015 at 10:25 AM, Daniel James < daniel.james at sourcefabric.org> wrote: > Hi Thomas, > > Let's start with HLS: > > - It's not a standard. It's current status is that it's an *expired* > > draft[1]. > > Does that suggest a lack of interest in an open standard? I'm actually not sure how it is expired... The most recent HLS

Hi Fred. Appreciate your response. Maybe in my explanation I have some red and green apples, but I can agree that my understanding is as you explained it. 😊 The point is that if I can successfully stream mp4 with H.264 and AAC encoding without any issues to icecast, I can then use ffmpeg to turn it into HLS which then solves my iOS support issue. The CPU cost of repackaging MP4 into HLS

Hi Wayne Yep, HLS is something we would like to use with Icecast. As you mentioned, Liquidsoap made a great step in the right direction if it comes to HLS. It seem that icecast might not get this support soon, as you might read in the discussion list. I don?t share these arguments, because we have real world use cases (we have many of them) where we would like use icecast with HLS support.

Hi, as there seems to be some interest in this topic, I'm opening a separate thread. Also please use proper in line comments and do NOT top post, as top posting breaks readability and discussion flow. Let's get some things out of the way: I'm going to acknowledge that HLS and DASH are things that are out there. Especially HLS is being pushed by the likes of Apple, in parts quite

Hi section 6.1 of R-exts suggests that a package can take over a function in the base package and make it generic. I want to do this with Re() and have the following lines in my R code: "Re" <- function(x){UseMethod("Re" )} "Re.default" <- get("Re" ,pos=NULL,mode="function") "Re.octonion" <- function(x){give.comp(x,1)}

R developers, 2 things: a bug in model.frame and a question about setup of generic functions. I don't understand the following behavior for generic functions: Suppose I'm working with the cats data in the MASS library and I want to create a formula object to model Hwt on Sex: # This works: > formula(Hwt ~ Sex) Hwt ~ Sex # But the following does not: > formula(Hwt ~ Sex,