This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [Patch, fortran] PR24398 - broken module files
- From: "François-Xavier Coudert" <fxcoudert at gmail dot com>
- To: "Paul Thomas" <paulthomas2 at wanadoo dot fr>
- 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 09:00:54 +0200
- Subject: Re: [Patch, fortran] PR24398 - broken module files
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EG0l0SGUCHIv13/ADEcnIZR+AQgxKR4HFqKVA+XIgNf89o4bjtqUsR96Sf7jNkEEudEggj4fzQoa164dzb1Y1LjigX/l/nkR98CzR/HdxZ9AIWBTnCqI5idVy4QmGsjioSQV4CTpVnBW2T8tDjIccmpNxnOHXsMUdXpghlL2NKQ=
- References: <452B9424.7010406@wanadoo.fr> <D7C43B27-1CFC-42AE-938F-444C1CE7F5DA@gmail.com> <452C8DA4.5000804@wanadoo.fr>
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?
I guess having (in module.c):
#define CURRENT_GCC_BRANCH 4.2
#define CURRENT_MODFILE_VERSION 7
would ensure that within each release series (4.2, 4.3, etc.) the
CURRENT_MODFILE_VERSION is the right condition to make decisions.
FX