Just pushed a new update to johnwcowan repo John Cowan 26 Aug 2019 13:35 UTC
Re: Just pushed a new update to johnwcowan repo hga@xxxxxx 26 Aug 2019 13:54 UTC
Re: Just pushed a new update to johnwcowan repo John Cowan 26 Aug 2019 16:20 UTC
Re: Just pushed a new update to johnwcowan repo hga@xxxxxx 26 Aug 2019 17:18 UTC
Re: Just pushed a new update to johnwcowan repo John Cowan 26 Aug 2019 18:05 UTC
Re: Just pushed a new update to johnwcowan repo Lassi Kortela 26 Aug 2019 18:11 UTC
Ports as an argument to file-info in the context of a required chase?/follow? hga@xxxxxx 26 Aug 2019 18:21 UTC
Re: Ports as an argument to file-info in the context of a required chase?/follow? John Cowan 26 Aug 2019 18:35 UTC
Re: Ports as an argument to file-info in the context of a required chase?/follow? hga@xxxxxx 26 Aug 2019 18:49 UTC
Assorted remarks on file procedures Lassi Kortela 26 Aug 2019 15:17 UTC
Re: Assorted remarks on file procedures hga@xxxxxx 26 Aug 2019 17:06 UTC
Re: Assorted remarks on file procedures John Cowan 26 Aug 2019 20:36 UTC
Real and effective uid/gid procedures in git master Lassi Kortela 26 Aug 2019 17:26 UTC
Re: Real and effective uid/gid procedures in git master John Cowan 26 Aug 2019 18:06 UTC
Re: Real and effective uid/gid procedures in git master hga@xxxxxx 26 Aug 2019 18:12 UTC
Re: Real and effective uid/gid procedures in git master John Cowan 26 Aug 2019 18:22 UTC
Re: Real and effective uid/gid procedures in git master hga@xxxxxx 26 Aug 2019 18:32 UTC
Re: Real and effective uid/gid procedures in git master John Cowan 26 Aug 2019 18:40 UTC
Re: Real and effective uid/gid procedures in git master Lassi Kortela 26 Aug 2019 18:45 UTC

Ports as an argument to file-info in the context of a required chase?/follow? hga@xxxxxx 26 Aug 2019 18:21 UTC

> From: Lassi Kortela <xxxxxx@lassi.io>
> Date: Monday, August 26, 2019 1:11 PM

>>     Lassi and I have I think agreed on that, with Lassi suggesting
>>     and my agreeing that file-info should default to chase?/follow?
>>     being false.

>> I believe it should not default, but be a required argument.  When
>> you ask for file info, you should have to think about what you
>> actually want.  That's the C-level status quo: there is no default
>> as between stat() and lstat() ,you have to pick one.

> That's even better.

Agreed, except:

> In C, fstat() for file descriptors is its own function as well.
> Should we simply mirror that in Scheme?

We currently do allow ports and necessarily use fstat.  We could
drop ports as a possible argument to file-info, that would make
the SRFI simpler to implement, and eliminate the following issue:

> Currently the chase argument is meaningless for ports.

Which poses a problem if we make it required across the board
(and we should decide RSN if it's going to be chase? or follow?).

We could make it quasi-optional, signaling an error if provided
with a port, or if not provided with a string.

Another option is a new procedure, something like file-port-info....

- Harold