similar to: Rgeneric.py assists in rearranging generic function definitions

Where should the setClass() ('methods' package) calls be placed in a package? I try to follow a one-class-one-file principe, but since setClass("ClassA", "ClassB") has to come a after setClass("ClassB", [snip]) it is not possible to fully follow this rule. So the best I can do now is to put all setClass() calls in a file named "000.R" (I know this

Late to the show on this release, unfortunately. One of our production packages no longer builds under R-2.15.0 with the following message. ** testing if installed package can be loaded Error: Function found when exporting methods from the namespace 'SuperCurve' which is not S4 generic: 'image' Possibly relevant clues follow: ## From R/AllGenerics.R if

Hi, I have a BioC infra-structure package that works fine (I can build, check and load it successfully) on revision r53950. The very same package fails on r54591 with the error below: Error in loadNamespace(package, c(which.lib.loc, lib.loc), keep.source = keep.source) : cyclic name space dependency detected when loading ?oligoClasses?, already loading ?oligoClasses? I don't see anything

Hello R-Team, May you help me to post a 'S4-creating Package Problem'? Thanks already now for supporting. The problem sounds like: Hello R forum, while compiling my R-package these 'Warnings' occur: ... Warnung in matchSignature(signature, fdef, where) : in the method signature for function "plot" no definition for class: "prediction" Warnung in

Hello everyone. R-2.12.0, suse linux 11.3. I am debugging a package that uses S4 methods and R CMD check gives the following warning: > Warning in methods::findMethods(g, env) : > non-generic function 'mdm' given to findMethods() > See the information on DESCRIPTION files in the chapter 'Creating R > packages' of the 'Writing R Extensions' manual. I

Hi So far when I have streamed Vorbis, the headers (the 3 first frames/packets) was not included in the stream, but communicated out of band typically in an SDP file as unparsed A-lines. Rethinking that concept, I'm wondering if it is really necessary to do it that way. Isn't it possible in a platform independent way to regenerate useable headers on the client side using just the

Hello. This question concerns the Methods package. I have created a new class and am trying to set a method for it for S4 group generic "Summary". I have run into some signature problems. An example: > setClass("track", representation(x="numeric", y="character")) [1] "track" > setGeneric("max", group="Summary")

Hi All I am using rsync to do a local network copy of 10 ~8gig files. The source is a NAS Atom rsync server, and the destination is a cygdrive, obviously on the same computer that is running rsync client. I am using --inplace, and ingeneral, the 8gig files generally have data changed within the file, but the general structure of the file is not changed. They are Firebird databases. (The total

I think the problem here is that the IR doesn't have any way to attach restrict information to loads/stores/pointers. It works on arguments because they can be given the 'noalias' attribute, and then the alias analyzer must understand what that means. Pete On Jan 24, 2012, at 7:47 AM, Roel Jordans wrote: > I have no clue, I didn't have time to look into that example yet.

Hi Roel, the code you list below is precisely what I expect to get (of course the stores must happen but the constant folding should happen as well). It all looks very strange. LLVM is behaving as if the __restrict__ keyword was not used at all. Even more strange is the fact that for this function: double f(double *__restrict__ x, double *__restrict__ y, double *__restrict__ z) { *x = 1.0;

Can you explain please why it works for this version of the function: double f(double *__restrict__ x, double *__restrict__ y, double *__restrict__ z); What is different here? There are stores here as well. Brent On Wed, Jan 25, 2012 at 12:34 AM, Roel Jordans <r.jordans at tue.nl> wrote: > Hi Brent, > > I think this is a problem in the easy-cse transform. In this transform

Hi Brent, I think this is a problem in the easy-cse transform. In this transform load operations can be replaced by their subexpression, in this case the propagated constant, based on the value of the 'CurrentGeneration' of memory writes. This implies that any store operation invalidates the knowledge about previously stored subexpressions. In general, this is a safe assumption but

I have no clue, I didn't have time to look into that example yet. How does the IR (before optimization) differ from the other version? Roel On 01/24/2012 04:45 PM, Brent Walker wrote: > Can you explain please why it works for this version of the function: > > double f(double *__restrict__ x, double *__restrict__ y, double > *__restrict__ z); > > What is different here?

Peter Cooper wrote: > I think the problem here is that the IR doesn't have any way to attach restrict information to loads/stores/pointers. I think we do now, actually. Now that the loads and stores have TBAA metadata, I think the restrict attribute can go there. It needs to be attached to every use of a restrict pointer, but that's similar to how TBAA already works. > It works

Hi I get this error with Rserve: eval failedeval failed, request status: R parser: syntax erroreval failed, request status: R parser: input incompleteorg.rosuda.REngine.Rserve.RserveException: eval failed at org.rosuda.REngine.Rserve.RConnection.eval(RConnection.java:233) at se.ucr.qrep.RGenerator.generateReport(RGenerator.java:45) Anyone know what it could mean? -- View this message in

I've rolled up R-2.8.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.8.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try

I've rolled up R-2.8.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.8.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try

I've rolled up R-2.9.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.9.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try

I've rolled up R-2.9.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.9.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try

The build system rolled up R-4.0.0.tar.gz (codename "Arbor Day") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard These are