| Re: Project sav file in 7.0 [message #61760 is a reply to message #60575] |
Tue, 29 July 2008 00:41  |
helaha
Messages: 26
Registered: March 2004
|
Junior Member |
|
|
Finally, I was able to solve the problems and want to post the
solution here. First, file name cases were not the problem
(WindowsXP). Second, the !path issue (bug), as mentioned by Robert
Moss, has been eliminated for the current IDL version 7.0.3. With this
version there appeared some (red marked) compilation errors in my
routines, which I had to eliminate. But there were still a few errors,
which were only shown, when I disabled the ITRESOLVE command.
Disabling the ITRESOLVE command led to a very detailed compilation
result, showing an extended list of routines and subroutines. But if
there was an error, the compilation stopped and only the routines
compiled so far were saved. Such an error appeared in the list without
a red marking just before the first “SAVE” line (and this could be in
the middle of a very long list). There is still an issue concerning
the resolving of all iTools routines. The only way to include both the
iTool routines and my own routines was following: Building the project
at first with the ITRESOLVE command enabled and then afterwards
building the project with the ITRESOLVE command disabled.
So the project building under IDL7 is far more accurate compared to
prior versions (e.g. 6.4). IDL7 stops compiling whenever a compilation
error appears whereas prior versions continued compiling.
Almost always some of my routines are under development and aren’t
really free of errors. As an example there was a wrong single “I” in a
command line. Therefore there appeared the error that the function or
routine “I” cannot be found. Now I can say that finding a single “I”
in several hundred routines and over 70.000 command lines is really a
challenge. The advantage is now, that my code is really error free.
Helmut Ahammer
MUG
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
