Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Effective Perl Programming: Ways to Write Better, More Idiomatic Perl 2nd ed.

by ack (Deacon)
on May 18, 2010 at 17:42 UTC ( #840554=bookreview: print w/replies, xml ) Need Help??
Order Effective Perl Programming: Ways to Write Better, More Idiomatic Perl 2nd ed.

Item Description: A series of Iteminized Suggestions for improving one's Perl programming

Review Synopsis: Super book! Much improved over 1st ed. Highly Recommend.

I loved the 1st edition of this book and couldn't wait to see this one when I fisrt saw that the authors, Joseph Hall, Joshua McAdams and Brian Foy were producing this 2nd edition. It was billed as a significant update with lots of new material and it is, in my opinion, exacly that.

This 2nd edition has a much more readable style (fonts, printing,etc, as well as style). The examples are, it seems to me, much improved and easier to both understand and digest.

The chapters on Unicode and on CPAN were especially interesting to me. But topics such as the chapter on Regular Expressions were all greatly improved. I especially like the chapter on Regular Expressions since it is a topic that has always been frustratingly opaque and obtuse to me...yet so often I have to try to use Regexs in my coding. This book's coverage of regexs is not extensive (it is not, of course, meant to be a tutorial on any of the topics); but the authors somehow...I can't seem to put my finger one it...managed in a few short pages to bring transparency to regexes for me like noone and no other book has!

Kudos to Hall, McAdams and Foy...Great job! I am confident anyone reading this book will not be disappointed.

UPDATE: Corrected some typos and re-did the formatting.

UPDATE 2: Corrected typos in Review Synopsis.

  • Comment on Effective Perl Programming: Ways to Write Better, More Idiomatic Perl 2nd ed.
Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: bookreview [id://840554]
[Corion]: But yes, "who started this process" is interesting information :)
[tye]: no, I really believe that "login user" was added as a fundamental bit of info about each process in order to enhance the usefulness of auditing
[Corion]: Ah - if that information is saved in a file, then you could theoretically spam that file and confuse getlogin(). So, don't use it for authentication :)
[tye]: that is what getlogin() certainly *used* to do. I don't believe that is what it certainly should do.
[davido]: /var/run/utmp is 664 i think.
[tye]: Note that my "man getlogin" says that it uses stdin when it should use /dev/tty (calling a glibc bug). But that does not appear to be the case when I test it. But maybe Perl's getlogin() is not using glibc's getlogin().
[oiskuu]: well, run a strace and see what the getlogin does for you.... As I said. SELinux probably has those security labels. But not regular linux.
[tye]: for example, read https://unix. questions/146138/ loginuid-should-be -allowed-to-change -or-not-mutable-or -not
[tye]: I'm not using SELinux and it certainly appears to disagree with you. shrug
[tye]: Since you brought up /proc, oiskuu, I didn't see you respond to my suggestion of 'loginuid'. Does your /proc not have such?

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (6)
As of 2017-06-23 19:46 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (554 votes). Check out past polls.