With respect to Perl5 objects, I would guess there are three things a Perl5 hacker would be interested in:
  1. A simple Perl5 vs. Perl6 example of syntax showing basic inheritance under Perl5 and Perl6
    • It will just give Perl5 hackers a reference point. "Oh, what used to be that now looks like that!"
  2. How can the new architecture be best used to improve existing code? Perhaps you could provide one or two examples of the "low hanging fruit."
    • Think about the question that current Perl5 coders will ask: "What is the motivation to change?"
  3. How will legacy code have to be changed?
    • For example, if you are using, say, a CPAN module that has been updated to the new object model, what are the most likely "gotchas" that will trigger errors?
    • Are there particularly widely used CPAN modules that you would expect to take full advantage of more restrictive typing or creative polymorphism (and thus possibly present some issues to legacy code)?
An alternative to sprinkling verbiage throughout the paper would be to create a 1-2 page appendix.

P.S. And add a table of contents.

In reply to Re^3: Perl 6 shocking revelations #1 by Starky
in thread Perl 6 shocking revelations #1 by John M. Dlugosz

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.