Re: [Rd] Problem with new("externalptr")

2008-01-29 Thread Robert Gentleman
Hi, Herve Pages wrote: > Hi, > > It seems that new("externalptr") is always returning the same instance, and > not a new one as one would expect from a call to new(). Of course this is hard > to observe: > > > new("externalptr") > > > new("externalptr") > > > since not a lot of detail

[Rd] R package Matrix failing to build with R-devel on Ubuntu AMD64

2008-01-29 Thread Mark W Kimpel
Switched back to R-devel tonight after using R-2.6.1 for awhile and when I updated my devel packages Matrix installation failed. Not critical for me but thought I should report it. I am using Ubuntu Gusty AMD64 OS. Tail of install output and sessionInfo follows. Mark Loading required package: m

Re: [Rd] Problem with new("externalptr")

2008-01-29 Thread Herve Pages
Luke Tierney wrote: > On Tue, 29 Jan 2008, Herve Pages wrote: > >> Hi again, >> >> Here is an example of an annoyance that I think is directly related to >> the >> problem with new("externalptr"). When you try to extend the >> "externalptr" class: > > You don't wnat to do that for the same reason

Re: [Rd] Problem with new("externalptr")

2008-01-29 Thread Luke Tierney
On Tue, 29 Jan 2008, Herve Pages wrote: > Hi again, > > Here is an example of an annoyance that I think is directly related to the > problem with new("externalptr"). When you try to extend the "externalptr" > class: You don't wnat to do that for the same reason you don't want to do it with envir

Re: [Rd] Problem with new("externalptr")

2008-01-29 Thread Herve Pages
Hi again, Here is an example of an annoyance that I think is directly related to the problem with new("externalptr"). When you try to extend the "externalptr" class: > setClass("ExternalInteger", contains="externalptr") [1] "ExternalInteger" then every call to new("ExternalInteger") will ret

[Rd] Problem with new("externalptr")

2008-01-29 Thread Herve Pages
Hi, It seems that new("externalptr") is always returning the same instance, and not a new one as one would expect from a call to new(). Of course this is hard to observe: > new("externalptr") > new("externalptr") since not a lot of details are displayed. For example, it's easy to see

Re: [Rd] "ROracle" Packages is not to be installed (PR#10652)

2008-01-29 Thread dhinds
[EMAIL PROTECTED] wrote: > /opt/oracle/product/10g/lib/libclntst10.a: file not recognized: File truncated Here: http://osdir.com/ml/lang.r.mac/2006-08/msg00031.html I found a suggestion to do this: $ cd $ORACLE_HOME/bin $ ./genclntst -- Dave __

Re: [Rd] Problem building R with Intel MKL v10 BLAS

2008-01-29 Thread Hin-Tak Leung
Prof Brian Ripley wrote: > On Mon, 28 Jan 2008, Hin-Tak Leung wrote: > >> Prof Brian Ripley wrote: >>> On Fri, 25 Jan 2008, Michael Braun wrote: >>> Thanks for everyone's help. Unfortunately, still no success. So I took the alternate route suggested in section A.3.1.5 of R-admin, >>>

[Rd] "ROracle" Packages is not to be installed (PR#10652)

2008-01-29 Thread bacycho
Full_Name: JinNyong Huh Version: 2.6.1 OS: Linux(SUSE-9.0) Submission from: (NULL) (220.75.209.235) ROracle Packages is not to be installed in my Linux. The enviroments are as follows: * O/S Profile [ export ORACLE_BASE=/opt/oracle export ORACLE_SID=DEMO10G export ORACLE_HOME=$ORACLE_BASE/produ

Re: [Rd] A "safe" do.call

2008-01-29 Thread hadley wickham
> > Or is this a bug in glm? It certainly seems that the documentation > > should mention that ... is passed to glm.control, which only takes > > three arguments. I realise that this doesn't come up very often > > during an interactive model fitting session, and it is easy to remedy > > when it d