From: Michael G. Schwern Date: Wed, 6 Mar 2002 16:20:27 +0000 (-0500) Subject: Re: [PATCH docs] Re: Bug with -M X-Git-Tag: accepted/trunk/20130322.191538~27733 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=95a3fe12cabdd424376b542e91e48eaae05c97fb;p=platform%2Fupstream%2Fperl.git Re: [PATCH docs] Re: Bug with -M Message-ID: <20020306212027.GC4257@blackrider> p4raw-id: //depot/perl@15072 --- diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 99caa88..63d12d7 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -294,9 +294,9 @@ X<-S>X<-b>X<-c>X<-t>X<-u>X<-g>X<-k>X<-T>X<-B>X<-M>X<-A>X<-C> -T File is an ASCII text file (heuristic guess). -B File is a "binary" file (opposite of -T). - -M Age of file in days when script started. + -M Script start time minus file modification time, in days. -A Same for access time. - -C Same for inode change time. + -C Same for inode change time (Unix, may differ for other platforms) Example: diff --git a/pod/perlport.pod b/pod/perlport.pod index bc3f1d9..fd0098a 100644 --- a/pod/perlport.pod +++ b/pod/perlport.pod @@ -262,6 +262,9 @@ timestamp (meaning that about the only portable timestamp is the modification timestamp), or one second granularity of any timestamps (e.g. the FAT filesystem limits the time granularity to two seconds). +The "inode change timestamp" (the <-C> filetest) may really be the +"creation timestamp" (which it is not in UNIX). + VOS perl can emulate Unix filenames with C as path separator. The native pathname characters greater-than, less-than, number-sign, and percent-sign are always accepted. @@ -1784,6 +1787,8 @@ as '', so numeric comparison or manipulation of these fields may cause mtime and atime are the same thing, and ctime is creation time instead of inode change time. (S) +ctime is creation time instead of inode change time (Win32). + device and inode are not meaningful. (Win32) device and inode are not necessarily reliable. (VMS)