[Rd] scan() doesn't like '1.#IND'

From: Hervé Pagès <hpages_at_fhcrc.org>
Date: Wed, 08 Feb 2012 17:59:22 -0800


Since C++ code compiled with g++ 4.6.3 on Windows (the version included in latest Rtools) now can produce things like '1.#IND' when writing doubles to a file (using the << operator), I wonder whether scan() shouldn't support those things. Right now (with recent R devel and latest Rtools) we get errors like:

   Error in scan(file, what, nmax, sep, dec, quote, skip, nlines, na.strings, :

     scan() expected 'a real', got '-1.#IND'

that we didn't get with previous versions of R devel and Rtools. See  


for the details. (Note that the file containing the numeric values is generated during the creation of the vignette.)

We don't see this error on Linux or Mac because on those platforms the C++ code will produce 'nan' or 'inf', which are supported by scan().


Hervé Pagès

Program in Computational Biology
Division of Public Health Sciences
Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N, M1-B514
P.O. Box 19024
Seattle, WA 98109-1024

E-mail: hpages_at_fhcrc.org
Phone:  (206) 667-5791
Fax:    (206) 667-1319

R-devel_at_r-project.org mailing list
Received on Thu 09 Feb 2012 - 02:05:12 GMT

This quarter's messages: by month, or sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

All messages

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Thu 09 Feb 2012 - 04:40:15 GMT.

Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-devel. Please read the posting guide before posting to the list.

list of date sections of archive