| Craig Dedo 2007-11-26, 7:17 pm |
| "Gary Scott" <garylscott@sbcglobal.net> wrote in message
news:IMB2j.65863$RX.58477@newssvr11.news.prodigy.net...
> mike.prager@noaa.gov wrote:
>
> Absolutely agree. Any translation must be by specific request of the
> application programmer.
> --
> Gary Scott
> mailto:garylscott@sbcglobal dot net
FWIW, I tried it using CVF 6.6.C, Lahey LF95 5.6, Silverfrost FTN95 5.10,
and G95 0.91. All of them interpret the backslash as a printable character,
**NOT** as an introduction to C-style escape sequences. Only GFortran 4.3.0 by
default interprets the backslash as an introduction to a C-style escape
sequence.
I agree with both Mike Prager and Gary Scott for the reasons that they
mention. Since backslash is a printable character in the Fortran charactder set
in Fortran 2003, any other interpretation of backslash violates section 1.5,
"Conformance", of the Fortran standard. The following sentence from Fortran
2003 1.5, paragraph 4 [2:35-36], is particularly relevant:
"A standard-conforming processor may allow additional forms and relationships
provided that such additional forms and relationships do not conflict with the
standard forms and relationships."
This language is unchanged from Fortran 95.
FWIW, the same idea is expressed in different language in C99, 4, par. 6 and
C++ 98, 1.4, par. 8.
--
Craig Dedo
17130 W. Burleigh Place
P. O. Box 423
Brookfield, WI 53008-0423
Voice: (262) 783-5869
Fax: (262) 783-5928
Mobile: (414) 412-5869
E-mail: <cdedo@wi.rr.com> or <craig@ctdedo.com>
|