The idea behind perlcc is not to secure your code. In fact securing web applications has much more to do with securing the server they are running on rather than trying to somehow make the code un-readable.

The idea behind perlcc (as i see it) is to make stand-alone applications for people who don't have and don't want to install a full-blown copy of Perl. That said I wish that perlcc was up to par to actually do that. Especially for distributing binarys to people on windows platforms who aren't going to know how to install Perl + needed modules + programs. For that there is PerlApp and Perl2Exe but both are commercial programs and for poor individuals like me are rather expensive :)

Lobster Aliens Are attacking the world!

In reply to Re: perlcc guidlines needed by cfreak
in thread perlcc guidlines needed by cknowlton

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.