From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [Fortran, committed] XFAIL read_dir.f90 on FreeBSD
Date: Tue, 01 Sep 2015 18:18:00 -0000 [thread overview]
Message-ID: <20150901181837.GA55508@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20150901181627.GA55465@troutmask.apl.washington.edu>
On Tue, Sep 01, 2015 at 11:16:27AM -0700, Steve Kargl wrote:
> open(unit=10, file='junko.dir',iostat=ios,action='read',access='stream')
> if (ios.ne.0) call abort
> read(10, iostat=ios) c
> - if (ios.ne.21) call abort
> + if (ios.ne.21) then
> + close(10)
I forgot to mention that 'close(10, status="delete')' does not
work on a directory. Should it?
> + call system('rmdir junko.dir')
> + call abort
> + end if
> + close(10)
> call system('rmdir junko.dir')
--
Steve
next prev parent reply other threads:[~2015-09-01 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 18:16 Steve Kargl
2015-09-01 18:18 ` Steve Kargl [this message]
2015-09-01 22:28 ` Jerry DeLisle
2015-09-02 8:30 ` Janne Blomqvist
2015-09-02 15:03 ` Steve Kargl
2015-09-03 21:58 ` Janne Blomqvist
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=20150901181837.GA55508@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).