Programming Perl, Third Edition, Slated for July

pudge on 2000-05-27T04:02:21

The third edition of the Camel (sometimes known by its secular title, "Programming Perl") is scheduled for July publication (possibly in time for Perl Conference 4.0, perhaps?). This edition is being penned by Larry Wall, Tom Christiansen, and Jon Orwant.

The month of May expects to see a third edition of Johan Vromans' Perl 5 Pocket Reference. Also coming up from O'Reilly in the next couple of months are David N. Blank-Edelman's Perl for System Administration and CGI Programming with Perl, 2nd Edition by Scott Guelich, Shishir Gundavaram, and Gunther Birznieks.


A bit early?

jdube on 2000-05-28T20:32:55

From what I hear from most people, their experiences with 5.6 included 'I upgraded, I saw, I downgraded.' I never checked it out because I heard it was insanely unstable, so I may be wrong here, but would it be viser to wait for some fixes, and possibly even for 5.7? No matter when it comes out, I'm definitly gonna buy it, I suppose, but I hope it covers a more-stable-than-5.6 Perl.

Re:A bit early?

pudge on 2000-05-28T21:35:58

Aside from threads, I have had no stability problems in 5.6. Some stuff just pukes on me with use5005threads enabled.

Re:A bit early?

padawan on 2000-05-28T22:43:28

I've tried to install DBI for 5.6, but no luck. DBI.xs threw up a lot of errors during make, and deja and the p5p mailing list shows that others experience problems as well. Is there a patch for DBI-1.13 or some other secret to get it to install?

BTW, does 5.6 work as the basis for mod_perl?

Re:A bit early?

jdube on 2000-05-28T23:04:54

hmm, mebbe I'll check it out then. Looks like there's a lot of fun stuff in there, if it works. Threads has always been a little crunchy, hasn't it?

Re:A bit early?

pudge on 2000-05-29T02:06:00

I had no problems at all with DBI and perl 5.6 (the perl 5.6 WITHOUT threads, that is). And I use it quite happily with mod_perl, too (though not on a production box, yet).

Re:A bit early?

jdube on 2000-05-29T02:14:07

Just upgraded about five minutes ago, played around a bit... looks good so far. Glad I did it. Hope the book is good... 400 or so new pages, wow, can't wait to see what they've added.

Programming Perl -Schwartz + Orwant, why?

havoclad on 2000-05-29T17:58:54

Does anyone have any info on why the change in authors was done?

Re:A bit early?

gbarr on 2000-05-29T18:17:54

Well I have lost count how amny hours I have spent tracking reported problems with my modules, only to find out that it was a 5.6 probelm. Now it is the first question I ask when someone reports a bug.

Re:A bit early?

alleria on 2000-05-30T14:36:13

Heh, on Win32, threads are still, well, a bit "crashy." ;)



Of course, given the black magic that was needed to make fork() work in the first place, and seeing as how they had to clone the entire interpreter, I think it's already very good.



Now if only they could get alarm() working for Windows ... :-P

Re:A bit early?

coreolyn on 2000-05-31T14:36:56

While at first install 5.6 appears to have too many problems to deal with. Headbanging seems to reveal that COMPLETE removal of old versions, libraries et all, coupled with a fresh compile from source (READING the README's), seems to eliminate the bulk of what at first glance appears to be problems

Installation on Solaris/veritas has revealed some issues but compiling perl with largefile support seems to resolve most of those issues.

5.6 has taught me that just because its labled 'stable' doesn't imply what I would define as 'stable', however, to make claims of being "insanely unstable" seems equally inaccurate.



In regards to a 3rd Edition of the camel . . . I'll be buying it (compulsive perl book collector). I hope it's an addition to my arsenal.

Re:Programming Perl -Schwartz + Orwant, why?

merlyn on 2000-06-12T17:42:06

Does anyone have any info on why the change in authors was done?
Yes. :-)

In truth, I cannot comment on this, as I would likely have to resort to foul language.