Say you implement this. Then you want to copy files which have ACLs (Access Control Lists) attached. Now you have to fix File::Copy again to copy the ACLs too. Tomorrow, what other file metadata will be employed at the filesystem level?
IMHO, it doesn't make sense to worry about tomorrow problems if you don't know what they will be (well, at least with a fair amount of probability). <AFAIK>ACLsare still different from OS to OS, and somewhere they can be considered experimental;</AFAIK> it is a moving target, that one can plan to address only where it is stable enough.
By the way, UNIX file permissions are there from the start, on every flavour of UNIX, and that problem on File::Copy should be addressed...
Ciao!
--bronto
The very nature of Perl to be like natural language--inconsistant and full of dwim and special cases--makes it impossible to know it all without simply memorizing the documentation (which is not complete or totally correct anyway).
--John M. Dlugosz
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
