gfortran.dg/pr16597.f90 leaves behind a file (bug?)

[Bud Davis]

i read the chapter in 'metcalf and reid', and could
not find an answer to this specific issue.

we first open a file with no name, thus it is 'fort.7'
then we close it.
then open it again, with status = scratch.

since it existed before the status = scratch open,
should it be deleted ?

my vote, and it is tentative, is that the file should
be destroyed because it is opened status = scratch.


--bud




--- "Kaveh R. Ghazi" <ghazi@caipclassic.rutgers.edu>
wrote:

>  > > Thanks for the confirm, I filed it as PR26802
> just now.
>  > 
>  > I closed it :)
>  > 
>  > This is not a bug. The first OPEN has neither
> FILE nor
>  > STATUS='SCRATCH' specifier, so it creates a file
> named fort.99 in the
>  > cwd. This is the expected behaviour.
> 
> Yes, I'm aware of that.
> 
>  > The testcase should probably have a
> STATUS='SCRATCH' added.
> 
> Err, but it does.  There are two open/close pairs,
> the second one
> opens fort.99 with STATUS='SCRATCH'.  Perhaps I'm
> exposing my neophyte
> fortran i/o skills, but shouldn't that cause fort.99
> to be deleted
> when the file is closed?
> 
> 		--Kaveh
> --
> Kaveh R. Ghazi			ghazi@caip.rutgers.edu
>