Return-Path: 
 <dev-return-4024-apmail-apr-dev-archive=apr.apache.org@apr.apache.org>
Delivered-To: apmail-apr-dev-archive@apr.apache.org
Received: (qmail 71074 invoked by uid 500); 21 Aug 2001 14:10:47 -0000
Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:dev@apr.apache.org>
List-Help: <mailto:dev-help@apr.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@apr.apache.org>
List-Subscribe: <mailto:dev-subscribe@apr.apache.org>
Delivered-To: mailing list dev@apr.apache.org
Received: (qmail 71054 invoked from network); 21 Aug 2001 14:10:47 -0000
Errors-To: <wrowe@rowe-clan.net>
Message-ID: <0b8a01c12a4a$aa570260$95c0b0d0@roweclan.net>
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
To: <Martin.Kraemer@Fujitsu-Siemens.com>, <dev@apr.apache.org>
References: <p05101001b7a63f5119f4@[192.168.0.16]>
 <035101c1293a$60e0ed00$95c0b0d0@roweclan.net>
 <20010821083633.A4748@deejai2.mch.fsc.net>
Subject: Re: file attribute questions
Date: Tue, 21 Aug 2001 09:07:49 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

From: "Martin Kraemer" <Martin.Kraemer@Fujitsu-Siemens.com>
Sent: Tuesday, August 21, 2001 1:36 AM


> On Mon, Aug 20, 2001 at 12:34:37AM -0500, William A. Rowe, Jr. wrote:
> > > * What is the difference between mtime and ctime? Also, would anybody have any use for creation date (as opposed to
modification
> > date)? I don't think anything outside the mac world uses creation dates.
> >
> > modified versus created (I think that answers your question.)  And yes, Win32 NTFS
> > and some other systems have ctime.  So does unix.
>
> Ehmmm.... As a nonWin32 enthusiast may I please interrupt here...

[enthusiast ;-?]

> It *may* be true that the windows API mis-interpreted the commonly
> accepted unix semantics for what the ctime field stands. In ALL unix
> systems, as well as in Linux, it stands for "time of last change to
> the inode".

Thanks for refocusing my understanding.

> <sarcast>
> I certainly do believe that microsoft had a hard time
> to fit that into the existing DOS and Win9x world, but then hey,
> the correct definition is clear.
> </sarcast>

msvcrt's 'struct stat' aside, MS has always spelled out that this is a file
creation time.  We fell in the trap of propagating their bs from their clib.
This will be fixed this week

Thank you for the detailed picture of unix ctime, I'll probably be trying some
other experiments myself to build on this.  Just out of curiosity, What apps
would ever rely on ctime?

Bill