Re: [Mingw-w64-public] Minor infelicity in pow() in 1.0

2011-11-23 Thread Ozkan Sezer
On Wed, Nov 23, 2011 at 9:54 AM, Kai Tietz wrote: > 2011/11/23 Ozkan Sezer : >> On Tue, Nov 22, 2011 at 11:30 PM, Prof Brian Ripley >> wrote: >>> Assuming you are still updating 1.0, this comes from a bug report on >>> R built with a toolchain from Sept 2010 (but the bug is still present >>> in t

Re: [Mingw-w64-public] Minor infelicity in pow() in 1.0

2011-11-22 Thread Kai Tietz
2011/11/23 Ozkan Sezer : > On Tue, Nov 22, 2011 at 11:30 PM, Prof Brian Ripley > wrote: >> Assuming you are still updating 1.0, this comes from a bug report on >> R built with a toolchain from Sept 2010 (but the bug is still present >> in the 1.0 branch). >> >> Suppose x is what is called in the C

Re: [Mingw-w64-public] Minor infelicity in pow() in 1.0

2011-11-22 Thread Ozkan Sezer
On Tue, Nov 22, 2011 at 11:30 PM, Prof Brian Ripley wrote: > Assuming you are still updating 1.0, this comes from a bug report on > R built with a toolchain from Sept 2010 (but the bug is still present > in the 1.0 branch). > > Suppose x is what is called in the C code MAXNUM, the maximum > normal

[Mingw-w64-public] Minor infelicity in pow() in 1.0

2011-11-22 Thread Prof Brian Ripley
Assuming you are still updating 1.0, this comes from a bug report on R built with a toolchain from Sept 2010 (but the bug is still present in the 1.0 branch). Suppose x is what is called in the C code MAXNUM, the maximum normalized double. Then pow(x, y) is computed as INF for 0 < y <= 1, whe