(j3.2006) Select Rank

Bill Long longb
Wed Feb 18 14:55:42 EST 2015

On Feb 18, 2015, at 10:10 AM, Keith Bierman <khbkhb at gmail.com> wrote:

> On Wed, Feb 18, 2015 at 12:57 AM, Malcolm Cohen <malcolm at nag-j.co.jp> wrote:
> ?...  fpp is better, but
> even so it's not official and not 100% portable.  And doesn't solve the tool
> problem.
> ?Well, the fpp source code is available, and reasonably portable.  If memory serves, it does put appropriate markings in the code that some tools (many debuggers) use to get the line numbering right.
> One hazard is on systems which don't properly supported mixed case file names, bork.F90 becomes bork.f90, and can clobber bork.F90 on line 1 of processing (got caught with this recently running Linux in a VM on a clients Windows system, where the source was in a shared folder, rather than inside the VM itself). An obvious approach would be to change the fpp processor to use .ftn and .f90 or some such?.
> ?But I take your point, it would be cleaner to have an all Fortran solution. I'm not sure I buy "INCLUDE" as being much more pure than #include, but the rest of the processing is where both the good and bad lies ;>?

In general (my opinion) a Fortran program that requires preprocessing, or uses included files (either spelling), or has a build process that is anything beyond a simple make file is most likely poorly designed.  


> _______________________________________________
> J3 mailing list
> J3 at mailman.j3-fortran.org
> http://mailman.j3-fortran.org/mailman/listinfo/j3

Bill Long                                                                       longb at cray.com
Fortran Technical Suport  &                                  voice:  651-605-9024
Bioinformatics Software Development                     fax:  651-605-9142
Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101

More information about the J3 mailing list