That looks like a Solaris quirk. Normalization of the values is not
required by the POSIX standard, nor by the other implementations we have
tested. The Solaris 7 man page does mention the restriction though.
We will change it for 2.3.0, thank you.
On Fri, 31 Mar 2006, Stephen C. Pope wrote:
I noticed that R was burning up 100% of a CPU when a call to Sys.sleep()
was made. Upon investigation, I discovered that R_checkActivityEx() in
src/unix/sys-std.c was putting the entire timeout (in usec) into the
struct timeval tv_usec member, leaving tv_sec set to 0.
I don't know about other u
Hi all,
In the CHANGES file for R-2.3.0alpha, there is the following
statement:
winMenuAdd() now has no limits on the number of menus or items, and
names are now limited to 500 (not 50) bytes.
However, I can reproducibly get a segfault using this (admittedly
silly) example:
for( i in 1:5) winMe
When I use
package?
the author field gets reproduced twice, once with the \author{ } string
and a secod time formatted.
Also, would it be possible to make package? find the overview
without the package being attached, or at least give a more informative
error message.
Paul Gilbert
=
The following approach
sobject <- charToRaw(serialize(object,NULL))
len <- length(sobject)
writeBin(sobject, outcon)
would appear to work. As from 2.3.0 you will then be able to do
unserialize(readBin(incon, "raw", n=len))
On Fri, 31 Mar 2006, Prof Brian Ripley wrote:
> I think you should be
I have two sets of time-series that I imported from Excel using RODBC
and placed in
"securities" and "factors".
What I need to do is generate t-scores for each security-factor pair.
I tried the following:
t1 <- t.test(securities[,3:42], factors[,2:41], var.equal=TRUE)
However,
The allocations described as User-Controlled are not part of the
GC-managed heap. The ones described as Transient happen to be but
that is not user visible; alternate implementations might insure that
they are freed as soon as the appropriate context is left.
If you are interested in managing the
You need to tell us what platform you're on, what compilers you're
using, etc. The details vary.
Duncan Murdoch
On 3/30/2006 10:56 PM, Steve Su wrote:
> Dear All,
>
>
>
> I have seen a number of e mails on this topic but I have not seen a
> general solution to date. I have Fortran and C sou
It is not a bug: please read the help file
xpd: logical. Should bars be allowed to go outside region?
and note that the default is TRUE.
On Fri, 31 Mar 2006, [EMAIL PROTECTED] wrote:
> There seems to be a bug in barplot(). It occurs when specifying the
> ylim argument. It's best shown b
Hi
There seems to be a bug in barplot(). It occurs when specifying the
ylim argument. It's best shown by example:
dat <- matrix(c(1,1,1,2,2,2,3,3,3),ncol=3)
barplot(dat, beside=TRUE)
X11()
barplot(dat, beside=TRUE, ylim=c(1,3))
As can be seem, drawing of the graph seems to discount the margins
> On Thu, 30 Mar 2006 18:23:11 +0100 (BST),
> Prof Brian Ripley (PBR) wrote:
> I have changed the default in save() to compress = !ascii. This seems
> quite safe, as almost always save() is called explicitly and people will
> appreciate that it might take a little time to save larg
11 matches
Mail list logo
