New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation for utime should be improved #2000
Comments
From Steve.Tolkin@fmr.comCreated by steve.tolkin@fmr.comThe documentation for utime should be improved, as follows: Please change the man page for the utime() function. Change perlfaq5 to have similar language, instead of the There was some discussion of this in In addition please add the words "utime" and "touch" to the *question* The point is to allow the command "perldoc -q touch" In general adding one or two words to the the question Ideally touch would also be added to the perlfunc man page, as a Steven Tolkin Perl Info
|
From [Unknown Contact. See original ticket]Created by steve.tolkin@fmr.comThe documentation for utime should be improved, as follows: Please change the man page for the utime() function. Change perlfaq5 to have similar language, instead of the There was some discussion of this in In addition please add the words "utime" and "touch" to the *question* The point is to allow the command "perldoc -q touch" In general adding one or two words to the the question Ideally touch would also be added to the perlfunc man page, as a Steven Tolkin Perl Info
|
From @ysth
Where? I don't see any such thing. |
From @tamiasOn Wed, Jun 07, 2000 at 07:25:26PM -0700, Yitzchak Scott-Thoennes wrote:
Steve may have meant import rather than export. =item import There is no builtin C<import> function. It is just an ordinary I don't think that touch and import are similar cases, however. import is Ronald |
From [Unknown Contact. See original ticket]Dear Ronald, My general objective in posting this (and a few others) to c.l.p.moderated I went looking to a function that did the equivalent of Unix "touch". I The entry for utime does mention touch, so if the man page was an plain old I want an entry such as "touch -- see utime". The question is, where to put One part of the solution is to use the word touch, and utime, in the We can always omit the string "in perl" from the questions, to save space. A more comprehensive approach would be to add other questions that use the It would be useful to extend the capability of perldoc to support multiple It would also be useful to add a new option meaning find all these strings I will post to perlbug, as a doc "bug", once I have a concrete suggestion to Steve
|
From @smpeters
My this is an old one. The below patch clarifies the FAT and HPFS The original discussion is in Inline Patch--- perlfaq5.pod.orig Mon Dec 13 23:12:59 2004
+++ perlfaq5.pod Mon Dec 13 23:49:37 2004
@@ -684,9 +684,14 @@
Error checking is, as usual, left as an exercise for the reader.
-Note that utime() currently doesn't work correctly with Win95/NT
-ports. A bug has been reported. Check it carefully before using
-utime() on those platforms.
+The perldoc for utime also has an example that has the same
+effect as touch(1) on files that I<already exist>.
+
+Certain file systems have a limited ability to store the times
+on a file at the expected level of precision. For example, the
+FAT and HPFS filesystem are unable to create dates on files with
+a finer granularity than two seconds. This is a limitation of
+filesystems, not of utime().
=head2 How do I print to more than one file at once? |
From @smpeters
My, this is an old one. The below patch clarifies the FAT and HPFS The original discussion is in Inline Patch--- perlfaq5.pod.orig Mon Dec 13 23:12:59 2004
+++ perlfaq5.pod Mon Dec 13 23:49:37 2004
@@ -684,9 +684,14 @@
Error checking is, as usual, left as an exercise for the reader.
-Note that utime() currently doesn't work correctly with Win95/NT
-ports. A bug has been reported. Check it carefully before using
-utime() on those platforms.
+The perldoc for utime also has an example that has the same
+effect as touch(1) on files that I<already exist>.
+
+Certain file systems have a limited ability to store the times
+on a file at the expected level of precision. For example, the
+FAT and HPFS filesystem are unable to create dates on files with
+ a finer granularity than two seconds. This is a limitation of
+filesystems, not of utime().
=head2 How do I print to more than one file at once? |
From @TuxOn Tue 14 Dec 2004 07:29, "Steve Peters via RT" <perlbug-followup@perl.org> wrote:
I removed the dangling space and added "the": Change 23647 by merijn@merijn-l1 on 2004/12/14 07:51:43 Subject: [perl #3274] [PATCH] Documentation for utime should be improved Affected files ... ... //depot/perl/pod/perlfaq5.pod#58 edit Differences ... ==== //depot/perl/pod/perlfaq5.pod#58 (text) ==== 687,689c687,694
-- |
From @smpeters
beta.google.com/group/comp.lang.perl.moderated/browse_thread/thread/632ef5480ef3a636/f274aa3de5040965?q=Win32+utime+Perl&_done=%2Fgroups%3Fhl%3Den%26q%3DWin32+utime+Perl%26qt_s%3DSearch+Groups%26&_doneTitle=Back+to+Search&&d#f274aa3de5040965
Applied as change #23647 as well as committed to the perlfaq cvs repository. |
@smpeters - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#3274 (status was 'resolved')
Searchable as RT3274$
The text was updated successfully, but these errors were encountered: