"I don't want to comment on TPF. Nothing wrong with TPF but if you want responses from different communities you should be willing to return to those communities in order to get responses."

Don't worry; I do pop in here from time to time.

I'm personally happy to respond to comments via any channel, but blog comments are TPF's official feedback mechanism, and TPF may not take into account (or even notice) feedback posted elsewhere.

"I don't understand why you need $4K to write a book."

Because I estimate that it will take around 300 hours to write, and cannot otherwise justify taking that much time off paid consulting, given that the end result will be given away freely, so I cannot expect to make much in the way of sales. At an hourly rate it works out well below normal market rates for either a programmer or a writer; indeed, it's barely above the UK legal minimum wage.

"I read this to mean you are going to teach me how to program OO Perl much the same way one would code in C#."

That's certainly not the intention. The C# book has a good chapter structure, and should be a good source of example classes to write. I'm fed up of writing "Employee is a subclass of Person" examples; the C# book has some great class names I could use, like Frog, and Room, and Employee. (Oh well... sometimes you can't escape these things!)

I draw your attention to the following quote from my grant application, which appears two paragraphs above the part you quoted:

"This would be written in a similar style to chromatic's Modern Perl book, following the same test-driven approach to development, but covering modern Perl OO programming tools, techniques, and patterns in greater depth."

So if you like Modern Perl, then I'd hope you would like this book too. And if you don't like Modern Perl, then I don't know what's wrong with you. ;-)

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

In reply to Re^2: Grant Proposal: Modern Object Oriented Programming in Perl by tobyink
in thread Grant Proposal: Modern Object Oriented Programming in Perl by tobyink

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.