|
From: | Dan Sebald |
Subject: | [Octave-bug-tracker] [bug #54622] test importdata fails in dev octave with windows |
Date: | Fri, 7 Sep 2018 17:45:09 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 |
Follow-up Comment #40, bug #54622 (project octave): I think that John might be experiencing a slightly different issue than Rik. See Comment #34, Comment #30 and Comment #4. The importdata.m script does tweak some post-dlmread things, but I can't find anywhere in the code where it re-interprets the Inf and NaN text fields. importdata.m just moves those fields into the textdata return value, so I can't see how anything would correct the NA coming from dlmread. The difference may be in the compiler/C-library used to build on your two systems and how it handles that <istream> >> double extraction operator: http://www.cplusplus.com/reference/istream/istream/operator%3E%3E/ The issue Rik sees in Windows (and probably John too if only it would get past the dlmread data problem) is something I can replicate on Linux if I force the same scenario. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?54622> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |