Over on R-help, the old problem of floating point precision has come up
again (see my example below, where calling RSiteSearch can change the
results of the var() function).
The problem here is that on Windows many DLLs set the precision of the
fpu to 53 bit mantissas, whereas R normally uses 6
I believe this to be a Windows-only problem. Setting the FPU control is
OS x CPU specific (e.g. Solaris and FreeBSD do it differently on Sparc and
ix86), and may well not be allowed for user processes.
But we should be more aggressive about combating it on Windows.
On Sat, 18 Feb 2006, Duncan
Hi,
on WinXP Pro SP2 with NTFS, I noticed that file.info() under
Rv2.2.1pat (2006-02-09) does not report the correct file size if the
file is >= 2^31 bytes (2GB). Is this problem known? Is this related
to the note in ?file.info:
"Some (broken) systems allow files of more than 2Gb to be created
I have found a strange scoping problem in Sweave. The following Rnw
file doesn't produce the same output in Sweave as it does if I produce
an R file using Stangle and execute that:
\documentclass[12pt]{article}
\begin{document}
<>=
election <- data.frame(A=1:3, B=9:7, C=rep(0,3))
partytotal <- re
Full_Name: Alok Krishen
Version: 2.2.1
OS: OS X
Submission from: (NULL) (68.221.92.169)
When install.packages("quantreg") produces the following error message
cannot create HTML package index in: make.packages.html()
__
R-devel@r-project.org mailing li
On Sat, 18 Feb 2006, Henrik Bengtsson wrote:
> Hi,
>
> on WinXP Pro SP2 with NTFS, I noticed that file.info() under
> Rv2.2.1pat (2006-02-09) does not report the correct file size if the
> file is >= 2^31 bytes (2GB). Is this problem known? Is this related
> to the note in ?file.info:
>
> "Some
On 2/18/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> On Sat, 18 Feb 2006, Henrik Bengtsson wrote:
>
> > Hi,
> >
> > on WinXP Pro SP2 with NTFS, I noticed that file.info() under
> > Rv2.2.1pat (2006-02-09) does not report the correct file size if the
> > file is >= 2^31 bytes (2GB). Is this
