Displaying 3 results from an estimated 3 matches for "ind00".
Did you mean:
ind0
2002 May 14
2
NaN/NA and sprintf double format
...bage when the number of decimal is specified while it
works fine for NA:
> sprintf("%.2f", NA)
[1] "0.00"
> sprintf("%.2f", NaN)
[1] "-1.#J"
Not specifying the decimal precision lets both print garbage:
> sprintf("%f", NaN)
[1] "-1.#IND00"
> sprintf("%f", NA)
[1] "-1.#QNAN0"
Is this a bug or a feature?
Dirk
--
According to the latest figures, 43% of all signatures are totally worthless.
--
According to the latest figures, 43% of all signatures are totally worthless.
-.-.-.-.-.-.-.-.-.-.-....
2012 Feb 03
2
Using Wintermute with Winebottler
...successfuly
18:54: Loading plugins...
18:54: wme_sample_pixel.dll
18:54: wme_snow.dll
18:54: wme_aMUSE.dll
18:54: Scanning packages...
18:54: Registered 0 files in 0 package(s)
18:54: Enumerating Direct3D devices...
18:54: Enumerating DirectSound devices...
18:54: Game aspect ratio: -1.#IND00
18:54: Monitor aspect ratio: 1.805360
18:54: Game aspect ratio is the same as monitor aspect ratio.
18:54: Backup resolution: 0 x 0
18:54:
18:54: Available video devices:
18:54: ATI Radeon HD 4600 Series (accelerated)
18:54: Driver: ati2dvag.dll 6.14.10.6764
18:54: Monitor: 0
18:54: Ava...
2002 May 16
0
Re: [R] NaN/NA and sprintf double format (PR#1561)
...get that on Linux too, but why is it fine? See below.
>
> > > sprintf("%.2f", NaN)
> > [1] "-1.#J"
> >
> > Not specifying the decimal precision lets both print garbage:
> >
> > > sprintf("%f", NaN)
> > [1] "-1.#IND00"
> > > sprintf("%f", NA)
> > [1] "-1.#QNAN0"
> >
> > Is this a bug or a feature?
>
> Remember that NA is logical, so this is not correct usage. Not that the
> correct usage works very much better ....
>
> The C code says
>
&g...