comment on

So, let's say you've read the Llama, the Alpaca, the Camel, the Panther, the Ram, and so on. Are you still looking for something? What haven't you found that you wanted?

I'd like a book which is actually about 'advanced' Perl programming. See my comments at Re: Advanced Perl Programming, 2nd edition -- more of the stuff in the first part of that book (e.g. globs, closures, attributes, Hook::Lexwrap, B, operator overloading, compilation phases), with greater detail and examples.

Among other things, I'd love a book entirely on XS. And probably a book entirely on POE.

To add to the laundry list of topics I'd like to see more detail on:

concurrent programming (forks, threads, multiprocessor) and IPC
software architecture/design for scalable Perl programming
unicode (in gory detail)
portability
security

I'm not saying there's a mass market for these things, but these come to mind when I think of things that seem to lack a well-written reference.

(And they do exist somewhere, please let me know so I can go check them out.)

Update:Some complaints I saw on another thread about how Perl is stereotyped as slow, for scripting only, etc., got me thinking maybe we need "Optimizing Perl" that would cover various problem domains including heavy I/O, database, CGI, numerical simulation, etc.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: What's missing in Perl books? by xdg
in thread What's missing in Perl books? by brian_d_foy

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.