Source programs are typically .pl or w/no extension (update: or .cgi), and modules will have the .pm extension. For modules, it matters and they schould always be .pm .. for scripts, it really doesn't matter. Personally, i usually name scripts foo.pl so i can at a ls glance see it's perl, but when i "install" it somewhere for real use, i will rename it and drop the extension and make sure it's executable. Depends if i want to run it like perl foo.pl or ./foo

as far as finding scripts, i would do a combination of searching for '.pl' and using the file command.. e.g. file /usr/bin | grep -i perl

as for associating files un linux/unix, if a text file is executable, it's not the extension that matters but what's one the first line of the file in the she-bang line (e.g. #!/usr/bin/perl).

In reply to Re: Conventional filename suffixes by davidrw
in thread Conventional filename suffixes by dbae

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.