From: "Atwood, Robert C" <r.atwood@imperial.ac.uk>
To: "Colin Tuckley" <colin@tuckley.org>
Cc: "John Love-Jensen" <eljay@adobe.com>, <gcc-help@gcc.gnu.org>
Subject: RE: gFortran problem compiling complex character strings
Date: Mon, 17 Dec 2007 15:29:00 -0000 [thread overview]
Message-ID: <2CB39EAF0E0EFF498ADEDA636B8C999F05574A9A@icex1.ic.ac.uk> (raw)
In-Reply-To: <47669020.9090709@tuckley.org>
colin> So it would appear that the Debian version of g77 does not
colin> have the 72 char
colin> limit.
Indeed, I cannot reproduce that on this Suse-10 system, if it fails wth
gfortran, and it also fails with g77. I copied your print statement,
with print starting in column 12, thus the closing single-quote is in
73, then just an 'end' after for a 2-line program
1 print *, 'Try one of "Skip", "Test", "Verbosity" or
"Cleanup"'
2 end
Both g77 and gfortran choke on it when not using any -ffree-form or
-ffixed-line-length= flags, and work if using the flag.
Did debain patch it so that it does not behave as documented? are the
documents patched too?!? I've got debian (lenny/sid) at home I can try
later on -- but probably I'm not going to be doing any fortran on that
machine.
(Also the editor I'm using (vim) handily places a nasty-looking yellow
blob over the offending quote when it's beyond the 72 columns!)
Versions:
GNU Fortran (GCC) 3.3.5 20050117 (prerelease) (SUSE Linux)
GNU Fortran 95 (GCC 4.0.2 20050901 (prerelease) (SUSE Linux))
GNU Fortran 95 (GCC) 4.2.0 20070130 (prerelease) <- my own build
Robert
next prev parent reply other threads:[~2007-12-17 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 16:10 Dominique Dhumieres
2007-12-15 16:17 ` John (Eljay) Love-Jensen
2007-12-15 16:36 ` Colin Tuckley
2007-12-17 14:09 ` Atwood, Robert C
2007-12-17 14:15 ` John Love-Jensen
2007-12-17 14:34 ` Atwood, Robert C
2007-12-17 15:05 ` Colin Tuckley
2007-12-17 15:29 ` Atwood, Robert C [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-14 8:53 Colin Tuckley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2CB39EAF0E0EFF498ADEDA636B8C999F05574A9A@icex1.ic.ac.uk \
--to=r.atwood@imperial.ac.uk \
--cc=colin@tuckley.org \
--cc=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).