> The big problem here is that Fortran programmers learn by looking at old
> code and trial-and-error, rather than reading languages documentation.
> The result is propagation of poor programming habits, and poor
> understanding of the language. The overlap between pointers and
> allocatables makes it hard to do the right thing based on
> trial-and-error. Hopefully, my Wiki summary will help.
You are probably right (and very polite).
> Bob's suggestion for module "constructors" and "destructors" is good.
> Some well-organized programmers require all modules to have both a
> constructor and a destructor, even if they don't really need one. Then,
> a script like Amber's "makedepend" will also generate source code that
> call all of the constructor and destructor routines, in an order that
> honors module dependencies. Or, if you don't want mandatory routines, a
> comment at the top of each module file can contain hints for the
> makedepend script.
Ah sure, one could probably come up with a number of ways to get around
of *some* Fortran shortcomings. I would not enforce mandatory init/fini
for modules though.
Have a great evening,
Volodymyr
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Apr 01 2009 - 01:10:45 PDT
