I think scanning a directory for files and making them executable without knowing what is really in there- is a security risk. If you already know what's in there, using chmod 0755 or whatever should not be a big deal.
I'm assuming here your ~/perl are scripts written- not something out of a package.

Consider putting your stuff in cvs/svn, making packages out of them- then you use your Makefile.PL to get those to install properly and chmod etc.

As for issue #1, I understand your point. I even agree. However, I feel this is a waste of time. For reference, may I suggest 'The Mythical Man Month' by Fred Brooks. He talks about this kind of thing. How coders are toolmakers, and when we go out to chop wood, we first sharpen the axe. Then we find a better way to sharpen the axe. Then we find a better way to prepare the better way to sharpen the axe. Then..

Anyhow. I think the solution for that shortcut you mention is better left to people writing the innards of perl itself. This is the kind of thing amateurs like us would just be shooting ourselves in the foot with.

++ For your ambition and curiosity. I applaude it.

In reply to Re: Some automation on Perlscripts? by leocharre
in thread Some automation on Perlscripts? by matze77

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.