C
Chris Theis
Hi all,
I'm currently facing something which is quite annoying and probably one of
you might have an idea of how to solve it efficiently. I have some software
(upon which I have no influence!!!!) which delivers data in scientific
notation and I have to read it. This is fairly simple, but here is the
tricky thing. This software is written in FORTRAN and shows the following
feature, which IMHO is rather a bug than a feature. If numbers get very
small like 7.0614E-238 it starts writing them out as 7.0614-238. So when I
parse the file what I get is 7.0614 because the minus is seen as a
separator. Of course I could start reading all the data a strings,
tokenizing them and start checking for this rather quirky behavior, but this
would slow down the process of reading the data which can be really huge!
Does anybody of you have an idea on how to "fix" this problem because I
cannot change the software which delivers these , IMHO corrupted values,
which are FORTRAN standard compliant.
Cheers
Chris
I'm currently facing something which is quite annoying and probably one of
you might have an idea of how to solve it efficiently. I have some software
(upon which I have no influence!!!!) which delivers data in scientific
notation and I have to read it. This is fairly simple, but here is the
tricky thing. This software is written in FORTRAN and shows the following
feature, which IMHO is rather a bug than a feature. If numbers get very
small like 7.0614E-238 it starts writing them out as 7.0614-238. So when I
parse the file what I get is 7.0614 because the minus is seen as a
separator. Of course I could start reading all the data a strings,
tokenizing them and start checking for this rather quirky behavior, but this
would slow down the process of reading the data which can be really huge!
Does anybody of you have an idea on how to "fix" this problem because I
cannot change the software which delivers these , IMHO corrupted values,
which are FORTRAN standard compliant.
Cheers
Chris