Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Beatnik (493)

Beatnik
  (email not shown publicly)
http://www.ldl48.org/
A 29 year old belgian who likes Mountain Dew, Girl Scout Cookies, Tim Hortons French Vanilla Flavoured Cappucinno, Belgian beer, Belgian chocolate, Belgian women, Magners Cider, chocolate chipped cookies and Perl. Likes snowboarding, snorkling, sailing and silence. Bach can really cheer him up! He still misses his dog.

Project Daddy of Spine [sf.net], a mod_perl based CMS.

In his superhero time (8.30 AM to 5.30 PM), he works on world peace.

Journal of Beatnik (493)

Friday November 25, 2005
02:24 PM

PHP 5.1.0

[ #27742 ]
From Slashdot (emphasis by me):

"A new release of PHP5 is available. This version includes over 400 bugfixes, performance improvements over the 5.0.x branch, new date handling code, new versions of PCRE/SQLite/PEAR and over 30 new core/extension functions. A number of security fixes are also present and users are recommended to upgrade."

I don't get it.. Adding 30 core functions? 30?? Did anyone ever think about just sticking those in some kind of module? With over 3000 core functions, how is anyone ever going to know everything about everything? I'm not sure how many bugfixes a general perl release has but 400 seems an awfull lot... Think there is a link between the number of bugs and the way I feel about PHP?

List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

PHP 5.1.0 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Why does anyone need to know "everything about everything" just because a function is "core" and not "in a module"? For a user (the programmer), the main difference between "core" and "a module" is that the module requires more work, as you have to require the module.

    As for 400 bug fixes... If each open ticket represents a bug, and each bug has an open ticket, then with 400 bug fixes a release, Perl will have closed its open tickets by release 5.16. That is, if no new bugs are found before 5.16 is release

  • That is going to make for one big PHP book! :)
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.