With respect to Perl5 objects, I would guess there are three things a Perl5 hacker would be interested in:
- 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!"
- 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?"
- 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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
