Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!samsung!think!linus!mbunix.mitre.org
From: cazier@mbunix.mitre.org (Cazier)
Newsgroups: comp.lang.fortran
Subject: write array
Message-ID: <112121@linus.mitre.org>
Date: 29 Jun 90 20:29:47 GMT
Sender: usenet@linus.mitre.org
Distribution: usa
Organization: The MITRE Corp., Bedford, MA
Lines: 16

I bumped into some code a few months ago that works on some compilers
but not all, yet the author claims the code to be completely portable.
As I rewrote the code to what I find to be 100% portable, I'm now curious
about the sample code shown below:

     write (...) KA 

where KA is really KA(j) where "j" goes from 1-n.
As I rewrote it, I simply used an implied do-loop and found the code
to work on those systems where where the original code would not, i.e.

     write(...) (KA(j), j=1,n)

Am I missing something about why the write (...) KA is supposed to be
portable? Is something wrong "standards"-wise with those compilers
which do not support such a construct?