Ticket #849 (closed todo: wontfix)

Opened 5 years ago

Last modified 3 years ago

OS.pmc - update file times

Reported by: jkeenan Owned by: jkeenan
Priority: normal Milestone:
Component: core Version: 1.3.0
Severity: medium Keywords: pmc
Cc: Coke, dukeleto Language:
Patch status: Platform: all

Description

This ticket formerly existed as  RT #38145. It was entered into RT by Coke on 3 Jan 2006. I am moving it to Trac at  the suggestion of whiteknight on his blog, which is also available at  (July 17).

Original description:

The OS pmc provides a mechanism for getting mtime and atime, but doesn't provide a mechanism to set them. (required, e.g. by tcl's [file atime] and [file mtime]

Here are some files that will be relevant to anyone working on this ticket:

src/pmc/os.pmc
t/pmc/os.t

Change History

in reply to: ↑ description   Changed 5 years ago by jkeenan

Replying to jkeenan:

The OS pmc provides a mechanism for getting mtime and atime, but doesn't provide a mechanism to set them. (required, e.g. by tcl's [file atime] and [file mtime]

Is what is being requested here anything other than an implementation of the Perl 5 utime() function?

If so:

(a) How do we resolve the ambiguities about utime and utimes mentioned in the BSD and Linux man pages?

BSD (via darwin): man utime

     This interface is obsoleted by utimes(2).

Linux: man utime

       POSIX.1-2001 marks utimes() legacy, which is strange since  it  provides  more
       functionality than utime().

(b) Can we do anything with the fact that we pick up i_utime -- but apparently not d_futimes -- from the Perl 5 %Config?

Thank you very much.
kid51

in reply to: ↑ description   Changed 4 years ago by jkeenan

Replying to jkeenan:

Here are some files that will be relevant to anyone working on this ticket: {{{ src/pmc/os.pmc t/pmc/os.t }}}

Now:

src/dynpmc/os.pmc
t/dynpmc/os.t

follow-up: ↓ 5   Changed 3 years ago by jkeenan

At the hackathon at YAPC::NA::2011, dukeleto and I discussed this ticket. duke pointed out that this ticket would require non-trivial platform-specific C code, not simply PIR. We wonder whether there is sufficient need for this feature in parrot core. If not, then we should reject the request.

Comments? I will close the ticket in 7 days if there is no request for the feature. If there is, we will need someone to handle it (in cooperation with others).

Thank you very much.

kid51

  Changed 3 years ago by jkeenan

  • cc dukeleto added
  • owner set to jkeenan
  • status changed from new to assigned

in reply to: ↑ 3   Changed 3 years ago by jkeenan

  • status changed from assigned to closed
  • resolution set to wontfix

Replying to jkeenan:

Comments? I will close the ticket in 7 days if there is no request for the feature. If there is, we will need someone to handle it (in cooperation with others).

There was no request, so I am closing the ticket. Thank you very much.

kid51

Note: See TracTickets for help on using tickets.