-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
readdlm improper handling of Int64 #9289
Labels
bug
Indicates an unexpected problem or unintended behavior
Comments
Cc: @tanmaykm |
I think we should use |
tanmaykm
added a commit
to tanmaykm/julia
that referenced
this issue
Dec 11, 2014
Used parseint, parsefloat and parse methods instead of float64_isvalid. Used parse method when an abstract type is specified.
tanmaykm
added a commit
to tanmaykm/julia
that referenced
this issue
Dec 11, 2014
Used parseint and parsefloat methods instead of float64_isvalid.
tanmaykm
added a commit
to tanmaykm/julia
that referenced
this issue
Dec 14, 2014
Used parseint instead of float64_isvalid.
tanmaykm
added a commit
to tanmaykm/julia
that referenced
this issue
Mar 18, 2015
Used tryparse methods instead of float64_isvalid. If return array is of Any type, try parsing as Int, Bool and Float64 before falling back to substring.
JeffBezanson
added a commit
that referenced
this issue
Mar 20, 2015
correctly parse integer types in readdlm. fixes #9289
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think this has been mentioned before, but I don't think an issue was submitted (or at least, I couldn't find it).
Namely,
readdlm()
improperly handles Int64.For example, given a text file consisting only of the line
-9223355253176920979
, readdlm gives the following incorrect result:The text was updated successfully, but these errors were encountered: