Found at http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/543dbbd5a3cb5fce
Jerry, could you check whether Richard Maine's concerns are correct or not? NAG f95 and g95 write everything in one line; g95 has also a trailing comma, NAG does not. (ifort 11beta and sunf95 don't support nml for internal files, yet.) For external files, g95 prints a newline before "/". (ifort and sunf95 print also in several lines, but without trailing comma.) ----------------- Richard Maine writes: ------------------------------ > C:\gcc_mingw64a\clf\nakelist>nakelist > &STUFF > N= 666, / That output showed up in the posting as being on two lines (at least in my newsreader). I hope that was an artifact of the newsgroup posting. If the compiler actually does something like put control characters (such as cr and/or lf) in the internal file, then that would be a bug. Also, the comma looks wrong to me. I don't think it is allowed. I suppose I'd need to study more carefully to be 100% sure, but the comma is a separator - not a terminator. That also looks like a bug, and one less likely to be a posting artifact. -- Summary: Namelist writting to internal files: Control characters wrong? Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36895