Re: R-alpha: .Machine object

Douglas Bates (bates@stat.wisc.edu)
Tue, 12 Nov 1996 17:29:22 -0600 (CST)


Message-Id: <m0vNSGg-000hhwC@franz.stat.wisc.edu>
Date: Tue, 12 Nov 1996 17:29:22 -0600 (CST)
From: Douglas Bates <bates@stat.wisc.edu>
To: Ross Ihaka <ihaka@stat.auckland.ac.nz>
Subject: Re: R-alpha: .Machine object
In-Reply-To: <199611122206.LAA26686@stat13.stat.auckland.ac.nz>
 <199611122206.LAA26686@stat13.stat.auckland.ac.nz>

>>>>> "Ross" == Ross Ihaka <ihaka@stat.auckland.ac.nz> writes:

  Ross> The S .Machine object seems to include all sorts of
  Ross> information I can't really see a use for (isn't virtually
  Ross> everything IEEE these days?).

But what about that 1 MIPS MicroVax sitting in the back of our "dead
computers" pile?  Are you telling me that I won't be able to bring R
up on that?  :-)

(Actually I can probably live without being able to bring R up on a
MicroVax.)

  Ross> I have some code which will certainly produce all this
  Ross> information, but it would be cleaner just to use the useful
  Ross> subset of values in <float.h> and <limits.h>.  We could give
  Ross> them the same names as the S values.

I think that is a good idea.  The most important ones are going to be
things like .Machine$double.eps and .Machine$double.xmax, etc.  Some
people may need to know .Machine$integer.max which will vary according
to 32/64-bit architectures but it is pretty weird code that needs to
adjust for that.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
r-testers mailing list -- To (un)subscribe, send
subscribe	or	unsubscribe
(in the "body", not the subject !)  To: r-testers-request@stat.math.ethz.ch
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-