http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40958
Harald Anlauf <anlauf at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gmx dot de
--- Comment #16 from Harald Anlauf <anlauf at gmx dot de> ---
(In reply to Dominique d'Humieres from comment #15)
> > However, the fundamental(?) issue of module sizes growing exponentially
> > with deep module hierarchies still remains. The solution to that is to
> > not include transitive dependencies, which in turn would require a module
> > cache for good performance. Whether that is worth doing, and who is willing
> > and able to do it, is unclear.
>
> Would not it be simpler to tell the users what they should do to avoid this
> issue? If yes, what would be the basic rules?
I doubt that this is the right answer. The user wants to write
maintainable and portable code. The paradigm of object-oriented
programming will more often lead to deeper module hierarchies
than simple code. You'd had a hard time to tell users that
gfortran requires to flatten those hierarchies when other compilers
don't (assuming that the others perform acceptably).
