Re: S16: chown, chmod

2008-11-23 Thread Aristotle Pagaltzis
* dpuu <[EMAIL PROTECTED]> [2008-11-24 00:40]: > I agree that the specific example of &chown.is_restricted is a > bad idea, but only because the POSIX API I was wrapping is > itself flawed. It is not flawed in the least, as far as the aspect we are talking about is concerned. (It is generally sane

Re: S16: chown, chmod

2008-11-23 Thread Brandon S. Allbery KF8NH
On 2008 Nov 23, at 18:35, dpuu wrote: On Nov 23, 2:33 pm, [EMAIL PROTECTED] (Aristotle Pagaltzis) wrote: The API you propose does not seem to me to shorten code at all and is likely to lead to problematic code, so it seems like a bad idea. Interfaces should be designed to encourage people to do

Re: S16: chown, chmod

2008-11-23 Thread dpuu
On Nov 23, 2:33 pm, [EMAIL PROTECTED] (Aristotle Pagaltzis) wrote: > The API you propose does not seem to me to shorten code at all > and is likely to lead to problematic code, so it seems like a > bad idea. Interfaces should be designed to encourage people to > do things correctly and to make it h

Re: S16: chown, chmod

2008-11-23 Thread Aristotle Pagaltzis
* Larry Wall <[EMAIL PROTECTED]> [2008-11-21 23:55]: > Any you could even do it in parallel: > > my @status = hyper map { .io.chmod($mode) }, @files > > though it's possible your sysadmin will complain about what > you're doing with the disk drive heads. :) Actually I/O subsystems are smart e

Re: S16: chown, chmod

2008-11-23 Thread Aristotle Pagaltzis
* dpuu <[EMAIL PROTECTED]> [2008-11-21 19:00]: > The definition of C includes the statement that it's not > available on most system unless you're superuser; and this can > be checked using a POSIX incantation. I was wondering if it > would be reasonable to provide this as a method on the chown > f