public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/29277] Formated stream output: Translate "\n" / achar(10) into "\r\n" on some platforms Date: Mon, 09 Oct 2006 03:07:00 -0000 [thread overview] Message-ID: <20061009030717.7637.qmail@sourceware.org> (raw) In-Reply-To: <bug-29277-1719@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-10-09 03:07 ------- Created an attachment (id=12398) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12398&action=view) Preliminaey patch for STREAM formatted read. There is a related problem with formatted stream read: program stream implicit none character(len=50) :: r1,r2 open(10,file='test.dat',form='formatted',access='stream',status='old') read(10,'(a)') r1 read(10,'(a)') r2 print *, ':',trim(r1),':' print *, ':',trim(r2),':' end program stream I have a preliminary patch for this that I would appreciate some testing on cygwin or other CR-LF type system. This is for the read only. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29277
next prev parent reply other threads:[~2006-10-09 3:07 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-28 22:39 [Bug fortran/29277] New: " tobias dot burnus at physik dot fu-berlin dot de 2006-09-28 23:23 ` [Bug fortran/29277] " jvdelisle at gcc dot gnu dot org 2006-09-28 23:37 ` jvdelisle at gcc dot gnu dot org 2006-10-04 5:28 ` jvdelisle at gcc dot gnu dot org 2006-10-04 6:28 ` jvdelisle at gcc dot gnu dot org 2006-10-09 3:07 ` jvdelisle at gcc dot gnu dot org [this message] 2006-10-09 3:39 ` jvdelisle at gcc dot gnu dot org 2006-10-13 1:30 ` patchapp at dberlin dot org 2006-10-13 1:41 ` jvdelisle at gcc dot gnu dot org 2006-10-18 4:04 ` jvdelisle at gcc dot gnu dot org 2006-10-18 4:08 ` jvdelisle at gcc dot gnu dot org 2006-10-18 6:03 ` jvdelisle at gcc dot gnu dot org 2006-10-18 7:01 ` patchapp at dberlin dot org 2006-10-18 23:13 ` jvdelisle at gcc dot gnu dot org 2006-10-18 23:24 ` jvdelisle at gcc dot gnu dot org
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=20061009030717.7637.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).