The best, practical copy protection is successful, even though it doesn't come close to solving the problem. The already high incidence of piracy would skyrocket if it weren't for software-based copy protection. School kids would be pirating twice as much software if it wasn't copy protected.

I found what's supposed to be one of the best Java decompilers. Here's a list of the bugs:

Cannot reliably sort out the extra arguments added to class constructors by Java compiler. Can generate constructors with an incorrect number of arguments or can fail to declare some local variables as final.

ZIP and JAR files are not supported. However you can unzip those files and decompile the whole class tree.

In those rare cases when unable to fully decompile constructs like labeled blocks with breaks or nested loops with inter-loop break/continue statements it generates the source with labels and goto statements which reflects program's control flow and displays the message "Couldn't fully decompile method <name>". Also when unable to reconstruct all try-catch-finally statements it displays the message "Couldn't resolve all exception handlers in method <name>".

Ignores the contents of the Line Number Table Attribute and the Source File Attribute.

Makes no use of the Java class hierarchy information. Consequently, always chooses java.lang.Object as a common superclass of two different classes and inserts auxiliary casts where necessary.

Doesn't handle inlined functions well.

Maybe there are commercial decompilers that work better, but price would be a roadblock to some potential piraters.

I want to pile on as many layers of protection as I can, especially when they're free and easy, as a compiler would be.

In reply to Re^19: Perl 6 ... dead? (no, just convalescing) by Wassercrats
in thread Perl 6 ... dead? by hartwig

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.