This is the mail archive of the
mailing list for the GCC project.
Re: [Patch, fortran] PR24398 - broken module files
- From: Paul Thomas <paulthomas2 at wanadoo dot fr>
- To: FX Coudert <fxcoudert at gmail dot com>
- Cc: "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>, patch <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 11 Oct 2006 08:22:28 +0200
- Subject: Re: [Patch, fortran] PR24398 - broken module files
- References: <452B9424.firstname.lastname@example.org> <D7C43B27-1CFC-42AE-938F-444C1CE7F5DA@gmail.com>
Here's something I've wanted to ask your for some time, and now is the
perfect occasion: do you think it would be good for us to include a
"version number" in the module files generated by gfortran, so that
when incompatible changes are made to the module file format, this
number can be bumped and gfortran can error out and ask the user to
regenerate the module file?
Thanks, and sorry if that's a stupid question,
If so, we are both in the same boat because I wondered the same thing,
when thinking about the check that the file being read is indeed a
module file. :-)
As it happens, I have not yet applied the patch because I am doing
house-husband duty and our daughter is unwell. A version number could
easily be added. I wonder what should trigger the number changes?
Changes to .mod files themselves, which would be my choice, or to the
library or the gcc version number? Since I could not see a reasonable
scheme, I did nothing.