Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29276 Discussions

0D 0A missing in f90-source produced by IDE

muppets
Beginner
1,840 Views
Hi all,
compling the attached subroutinegave me very strange errors, such as "found identifier when expecting end-of-statement" and I was not able to find any syntax error. Inserting an additional comment line lead to a successfull compile run, but to a strange behaviour of the debugger. The yellow arrow passed to positions where no exectable statement were but to empty lines.
Then I opened the source file using WinHex and realized that some lines were not terminated by the bytes 0D 0A but only with a single 0D. My next step was to open the source file with Notepad and saw that the concerning lines were in one single line within NOTEPAD, deliminated by a rectangle symbol. Deleting this rectangles and hitting the RETURN key in each case repaired the source file and it worked from then on in the normal way in the IDE, too.
Does anybody have some ideas what was goeing wrong there? I have attached the erroneous source file which was produced using the IDE.
Thank you in advance
muppets
0 Kudos
8 Replies
Steven_L_Intel1
Employee
1,840 Views
In my experience, VS.NET can edit files with the UNIX convention (just CR terminator), and it leaves them that way. I imagine the compiler may get confused if you have a mix.
0 Kudos
muppets
Beginner
1,840 Views
Dear Steve,
thank you so much for your super fast answer. Probaly you are right, but I'm not aware having ever changed something to UNIX conventions. WherehadIput my hands where I'd better pulled them away?
Thank you again
muppets
0 Kudos
Steven_L_Intel1
Employee
1,840 Views
I don't know - perhaps if you edited the file with some UNIX text editor? I've never run across this problem myself, and have edited a lot of files in UNIX format, but I have never seen a mix of terminators.
0 Kudos
muppets
Beginner
1,840 Views
Steve,
this file was produced definitly only using the Microsoft VS.NET IDE.
Regards, thank you
muppets
0 Kudos
Steven_L_Intel1
Employee
1,840 Views
No idea, then. Sorry.
0 Kudos
muppets
Beginner
1,840 Views
Never mind, I found a workaround repairing this source file using notepad.
Thank you very much again
muppets
0 Kudos
aliho
Beginner
1,840 Views
Open your source files with MFC Wordpad (wordpad.exe) and save them. All 0d will be changed in 0d0a.
0 Kudos
muppets
Beginner
1,840 Views
Perfect! It works almost automatically! Were you ever been faced with this or a similar prob?
Greetings, thank you
muppets
0 Kudos
Reply