Re: [Rd] Allow semantic versioning for packages

On Mon, Oct 7, 2013 at 6:32 PM, Simon Urbanek wrote: > On Oct 5, 2013, at 9:19 PM, Gábor Csárdi wrote: > [...] > e.g. quoting the spec: "Build metadata SHOULD be ignored when determining > version precedence." > Indeed, although 'SHOULD' means that it is only a recommendation. And the build met

[Rd] uninformative error message when building package: ‘x’ must be an atomic vector

Hi, When building this Bioconductor package with R-devel: http://www.bioconductor.org/packages/devel/bioc/src/contrib/ROntoTools_1.1.2.tar.gz I get the following: [...] Error: processing vignette ‘rontotools.Rnw’ failed with diagnostics: ‘x’ must be an atomic vector Execution halted If I insta

Re: [Rd] Allow semantic versioning for packages

On Oct 5, 2013, at 9:19 PM, Gábor Csárdi wrote: > On Sat, Oct 5, 2013 at 2:23 PM, Simon Urbanek > wrote: > Gabor, > > On Oct 5, 2013, at 4:58 PM, Gábor Csárdi wrote: > > > Simon, > > > > I think there is a misunderstanding here. I am not suggesting anarchy, > > completely the opposite. > >

Re: [Rd] R 3.1.0 and C++11

Hi Martyn, On 7 October 2013 at 21:18, Martyn Plummer wrote: | I don't see any harm in allowing optional C++11 support, That would be a nice step forward. | and it is no trouble to update the documentation to acknowledge the | existence of C++11 conforming compilers. Indeed. | However, the qu

Re: [Rd] R 3.1.0 and C++11

I don't see any harm in allowing optional C++11 support, and it is no trouble to update the documentation to acknowledge the existence of C++11 conforming compilers. However, the questions of what is possible, what is recommended, and what is required for CRAN submissions are distinct. I have a

Re: [Rd] C++ debugging help needed

On 07/10/2013 12:18 PM, Martyn Plummer wrote: Yes, on reflection it's an ABI problem on Linux (use of PIC code in shared libraries means that any symbol can be interposed). Using namespaces isn't really the answer because that's an API issue. I think what you really need to do is control the vi

Re: [Rd] C++ debugging help needed

Yes, on reflection it's an ABI problem on Linux (use of PIC code in shared libraries means that any symbol can be interposed). Using namespaces isn't really the answer because that's an API issue. I think what you really need to do is control the visibility of your classes and functions so that e

[Rd] SOLVED: search for variable in package in .GlobalEnv first

Duncan Murdoch writes: > On 07/10/2013 10:29 AM, Rainer M Krug wrote: >> Hi >> >> First, sorry if I get the terminology wrong, I am still quite new to the >> concept of using environments and workspaces. >> >> Say I have a statement in a package SIM like >> >> sim <- TYPE >> >> where the variable

Re: [Rd] search for variable in package in .GlobalEnv first

On 07/10/2013 10:29 AM, Rainer M Krug wrote: Hi First, sorry if I get the terminology wrong, I am still quite new to the concept of using environments and workspaces. Say I have a statement in a package SIM like sim <- TYPE where the variable TYPE is initialized in the package to e.g. "expone

[Rd] search for variable in package in .GlobalEnv first

Hi First, sorry if I get the terminology wrong, I am still quite new to the concept of using environments and workspaces. Say I have a statement in a package SIM like sim <- TYPE where the variable TYPE is initialized in the package to e.g. "exponential" (SIM::TYPE == "exponential"). Now, I wa

[Rd] [Windows] Behaviour of shell on error

Hi, on my R-3.0.2 windows (32bits) no error is thrown occurs when calling a shell command with intern=TRUE, mustWork=TRUE. Is this a intended/known behaviour? >From the source of base::shell it is clear that mustWork is only used when intern=FALSE. This is not that clear from the help page: " Ar

[Rd] SOLVED: check warning with .onLoad() and setClass()

Thanks John and Dirk for your input. I solved the problem by importing the package "simecol" which defines the superclass simEcol in the NAMESPACE file with import(simEcol) and to leave it in the DESCRIPTION file in the Depends section (as the functions have to be available for the end user). I r

Re: [Rd] Compiler warning: function returns address of local variable

> > ..., my previous > > dev-lang/R-2.10.1 ebuild package has been upgraded to R-3.0.1. > > While compiling it, I have got the following compiler warning: > > > > * QA Notice: Package triggers severe warnings which indicate that it > > *may exhibit random runtime failures. > > * m

Re: [Rd] Compiler warning: function returns address of local variable

On 05/10/2013 20:48, Gevis Inko wrote: I am a Gentoo user. I have just upgraded my Gentoo system, as I usually do every Saturday. During this process, my previous dev-lang/R-2.10.1 ebuild package has been upgraded to R-3.0.1. While compiling it, I have got the following compiler warning: * QA