Re^3: Perl 6 shocking revelations #1

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.

Comment on Re^3: Perl 6 shocking revelations #1

Replies are listed 'Best First'.
Re^4: Perl 6 shocking revelations #1 by BrowserUk (Patriarch) on Apr 28, 2008 at 06:45 UTC
P.S. And add a table of contents. But only if the references in the toc are clickable links. Most of the pdfs I read that have tocs are dead text and give references in units, be they page numbers or chapter or section numbers, that bear no relationship to the actual pages as displayed in the bookmark section. Which makes them all but useless. Just so much extra junk that must be navigated to get to the real article. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^5: Perl 6 shocking revelations #1 by John M. Dlugosz (Monsignor) on Apr 28, 2008 at 12:24 UTC
My thoughts exactly. PDF doesn't have separate screen/print views like HTML CSS, by design, so I can't have a print-only TOC. I added a brief TOC that's not pages and pages long, and turned on the live navigation in the default view.	[reply]
Re^5: Perl 6 shocking revelations #1 by blazar (Canon) on Apr 28, 2008 at 16:08 UTC
Most of the pdfs I read that have tocs are dead text and give references in units, be they page numbers or chapter or section numbers, that bear no relationship to the actual pages as displayed in the bookmark section. I personally believe that as an old time LaTeX aficionado I should beg to differ. I find that most documents compiled with hyperref and either the standard classes or memoir.cls (and surely the Koma ones as well, although I have no experience with them) come out with all sorts of appropriate hyperlinks in the toc and elsewhere. Of course, like anything else in LaTeX, one may have to fiddle with some setting to fine tune the appearance of them and some other details. In this sense, most articles on arXiv are also duly hyperlinked. `--` If you can't understand the incipit, then please check the IPB Campaign.	[reply] [d/l]
Re^4: Perl 6 shocking revelations #1 by John M. Dlugosz (Monsignor) on Apr 28, 2008 at 12:22 UTC
Table of contents: Click on the icon to display the TOC or page thumbnails. Or do you specifically need an inline table for printing? I didn't think of that. I applied some of your ideas in version 1.1, which I updated at the URL. —John	[reply]
Re^5: Perl 6 shocking revelations #1 by Starky (Chaplain) on Apr 30, 2008 at 14:47 UTC
The "Perl 6 syntax" table at the top of page 3 is extremely helpful, as is the TOC. Overall, a fun read and a nice piece of work.	[reply]


"be consistent"
	PerlMonks