This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/57360] Implement a warning for implied save
- From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 22 Oct 2015 05:45:09 +0000
- Subject: [Bug fortran/57360] Implement a warning for implied save
- Auto-submitted: auto-generated
- References: <bug-57360-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360
Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Joost.VandeVondele at mat dot ethz
| |.ch
--- Comment #3 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to Harald Anlauf from comment #2)
> I have a quite common "counter example"
> Should this one also get a warning?
yes, while there are plenty of good uses of saved variables (really?), it
should be made more explicit i.e. just write
logical, save :: first = .true.
as often with warnings, expert programmers won't need them, but novices might
(and they are useful to enforce good coding style with -Werror=foo). It is
certainly something I would add to the enforce list for our project.