Re: apr_finfo_t ctime field

[Branko Čibej <br...@xbc.nu>]

William A. Rowe, Jr. wrote:

>As we approach APR 1.0
>
>---
>
>is it time to address the ambiguity between ctime, which is actually the
>inode file time stamp for unix, and the creation time stamp for win32?
>
>Persisting either ctime will propogate the confusion, I suggest splitting
>them into intime and crtime.  Opinions?
>
>I'll offer an APR 1.0 patch tommorow based on feedback.
>  
>
Yes, yes, yes. Sorry I didn't notice this before. This would be a very 
good change.

-- Brane

Re: apr_finfo_t ctime field

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

Wow - and time is almost gone.  Sorry this got no response until today,
I'm not sure the powers that be really care for this change to go in until
2.0 at this point (it's an eliminated ctime and added crtime & intime
member of a transparent structure that's user-allocated.)

Would be really nice to see one more bit of feedback before I commit
such a change - amazes me we are the only two folks considering
this issue.  Sander Striker on 4/27/03 and Brian Pane the day after
pondered this a while, but apparently we are the only two with any
real concern about the ambiguity.  Anyone else care to chime in?

At 06:28 PM 7/1/2004, Branko Čibej wrote:
>William A. Rowe, Jr. wrote:
>
>>As we approach APR 1.0
>>
>>---
>>
>>is it time to address the ambiguity between ctime, which is actually the
>>inode file time stamp for unix, and the creation time stamp for win32?
>>
>>Persisting either ctime will propogate the confusion, I suggest splitting
>>them into intime and crtime.  Opinions?
>>
>>I'll offer an APR 1.0 patch tommorow based on feedback.
>> 
>Yes, yes, yes. Sorry I didn't notice this before. This would be a very good change.
>
>-- Brane