apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <sterl...@covalent.net>
Subject RE: [PATCH] apr_file_mktemp should APR_CREATE the tmp file
Date Fri, 18 Jan 2002 02:58:01 GMT
On Fri, 18 Jan 2002, Ryan Bloom wrote:

> > > Yeah, I agree that it is different, but I'm not entirely sure that
> > > it is the wrong thing to do.  I think if you have a temp-file, you
> > > want to delete it by *default*.  Since a user can override those
> > > flags, I think it's NBD as well.  -- justin
> >
> > IIRC... you can add the DELONCLOSE flag, but you cannot _UNDO_ flags
> > you didn't want.  We need to remove the DELONCLOSE flag and let the
> > user pass it, if they want to always blast the file on close.
>
> If you pass any flags, you are taking ownership of all flags, which
> means that if you decide to pass in a set of flags, you will overwrite
> the defaults, you will not augment them.
>
> > Temp files aren't always the lifetime of a single open command.  And
> > the mktemp file is often used to create permanant, unique files.
>
> I am fine with either deleting by default or not deleting by default.

I say we don't delete on close by default..... its not very intuitive for
people used to mkstmp (i was caught by this already).

Again, if they want it, they can pass flags.

sterling


Mime
View raw message