Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
We have IDL at work but only on one machine so I thought it would be good to give gdl a try.I don't have a lot of experience with the GDL language and I usually use OCTAVE or R. The thing is that someone gave me a huge script to postprocess data and there is no way I would have time to rewrite it. The script run fine under IDL version 8 but crashes with GDL with some "input conversion errors".
I managed to isolate the pb and it seems to come froø the way IDL/GDL read an input ascii file:
let's assume I have a text.txt file that looks like this:
4 5 6 ! some comments
7 8 9 10 ! some comments
! some comments
if I use the following code:
for ii=1,ii=4 do readf,uu,jj print,jj
IDL version 8 returns: 1, 2, 4, 7
GDL returns, 1,2,3,4
My problem is that the script I have intensively uses the IDL way to skip information (and comments) from input files...
Would that be possible to get the same behavior in GDL with minimum change to the script
Thanks a lot
Thanks you reporting this bug.
Which version of GDL do you use ? (print, !gdl)
This bug did exist long ago, it is now solve
since about one year.
compiling the CVS version is rather simple on recent Linux distros,
as long as cmake is recent (> 2.8.4) and plplot too