------- Comment #1 from kargl at gcc dot gnu dot org 2010-01-05 05:49 ------- (In reply to comment #0) > [forwarded from http://bugs.debian.org/501560] > > "gfortran documentation lacks any kind of info about how to create a module > .mod file. It should be quite easy to indicate that the standard gcc option -c > when applied to the to-be-compiled file creates the .mod file along with the > .o > file." > > should -c explain how a .mod file is created?
IMHO, the answer is a resounding 'no.' Adding such information would simply add unneeded clutter to the manual, and should be an insult to anyone that uses Fortran. Also, the Fortran standard does not require that a .mod be created, and with -fwhole-file it is entirely possible that gfortran can keep the module information in memory while compiling a program and never emit anything. In fact, the intrinsic modules specified in the standard (that gfortran has implemented) do not exist as files. These are built on the fly. Should we also explain to the user that 'fire is hot and water at room temperature is wet.'? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607 ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
