Re: [PHP-DEV] About optimization
> This isn't about server costs. It is about choosing the right tool for > the right part of the job. A Javascript library for the client-side > frontend, PHP for the server-side frontend, C/C++ for your middle-layer > and an appropriate datastore behind it all and you can build amazing > things with PHP. The largest destinations on the Web today are written > exactly like this. This is a tremendous insight. No where near my experience. (Neither is cheap hosting for individuals). Faster PHP means smaller webfarm, and if you pay for that webfarm, then these things matter. At any rate, thanks for the long description. And I do notice the nice tone in contrast to mine that day. Sigh... > All I can say on this is, send some patches to the list. PHP improves > through code. True, true. But I remember a history of push back to such things, and even if now that is no longer the case, the price of political engagement is too high (that is, just explaining the stuff, etc). We're at the point of migrating away (in small tiny steps) anyhow, but I hope others that have experience and extra manpower speak up. There are some interesting internal forks of php out there that are cleaner and faster than what we could contribute anyhow. > It seems that you did not look closely to the improvements made to PHP 5.3. Sadly, I'm not sure 5.3 is in the cards for this year, and the stock build wouldn't do. Needs work on method dispatch. iamstever -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 5 Bug Summary Report
Hello, Those are some good ideas, another thing I think might help get some bugs closed is a way to detect which bugs have patches/diffs attached or included. Honestly I stopped submitting patches when I noticed they rot for months :) -Chris On Jan 25, 2010 9:37 AM, "Guilherme Blanco" wrote: I usually look at the count of issues and compare to the previous week. Then after a quick eye-"diff", I check which ones were fixed. I think I'm the only one that does that... =) Your changed would be very well accepted, specially by me. Cheers, On Mon, Jan 25, 2010 at 2:26 PM, Philip Olson wrote: > > On Jan 25, 2010, at ... -- Guilherme Blanco - Web Developer CBC - Certified Bindows Consultant Cell Phone: +55 (16) 9215-8480 MSN: guilhermebla...@hotmail.com URL: http://blog.bisna.com São Paulo - SP/Brazil -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/...
Re: [PHP-DEV] PHP 5 Bug Summary Report
I usually look at the count of issues and compare to the previous week. Then after a quick eye-"diff", I check which ones were fixed. I think I'm the only one that does that... =) Your changed would be very well accepted, specially by me. Cheers, On Mon, Jan 25, 2010 at 2:26 PM, Philip Olson wrote: > > On Jan 25, 2010, at 1:30 AM, internals@lists.php.net wrote: > >> PHP 5 Bug Database summary - http://bugs.php.net/ >> >> Num Status Summary (1595 total -- which includes 1036 feature requests) > > Curious, does anybody use or read these? These emails have probably outgrown > their use, so let's evaluate: > > - Reasons for removal: The content is overwhelming, and does clutter the > list search results > - Reasons for changing: Same as above, and good ideas would result > - Reasons for keeping: Old timers like old things, it reminds us that we > have many bugs, and ^f > > Like, they could instead show simple statistics similar to ones presented > here: > > - http://bugs.php.net/lstats.php?phpver=5&per_category=1 > - http://bugs.php.net/bugstats.php?phpver=5 > > And while doing this, we could show how many were open/closed the previous > week. I think I just volunteered to make that happen, if desired by others. > > Other ideas (some crazier than others): > > - Show who closed bugs (positive) > - Show how long bugs have been assigned to people (negative) > - Show the top 5 buggiest and bug free extensions (both) > - ... > > Hopefully others have ideas, especially for positive reinforcement as it > unfortunately feels much easier to come up with negative ones. But, that's > okay too. ;) > > Regards, > Philip > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Guilherme Blanco - Web Developer CBC - Certified Bindows Consultant Cell Phone: +55 (16) 9215-8480 MSN: guilhermebla...@hotmail.com URL: http://blog.bisna.com São Paulo - SP/Brazil -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 5 Bug Summary Report
On Jan 25, 2010, at 1:30 AM, internals@lists.php.net wrote: > PHP 5 Bug Database summary - http://bugs.php.net/ > > Num Status Summary (1595 total -- which includes 1036 feature requests) Curious, does anybody use or read these? These emails have probably outgrown their use, so let's evaluate: - Reasons for removal: The content is overwhelming, and does clutter the list search results - Reasons for changing: Same as above, and good ideas would result - Reasons for keeping: Old timers like old things, it reminds us that we have many bugs, and ^f Like, they could instead show simple statistics similar to ones presented here: - http://bugs.php.net/lstats.php?phpver=5&per_category=1 - http://bugs.php.net/bugstats.php?phpver=5 And while doing this, we could show how many were open/closed the previous week. I think I just volunteered to make that happen, if desired by others. Other ideas (some crazier than others): - Show who closed bugs (positive) - Show how long bugs have been assigned to people (negative) - Show the top 5 buggiest and bug free extensions (both) - ... Hopefully others have ideas, especially for positive reinforcement as it unfortunately feels much easier to come up with negative ones. But, that's okay too. ;) Regards, Philip -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 6 Bug Summary Report
PHP 6 Bug Database summary - http://bugs.php.net/ Num Status Summary (108 total -- which includes 47 feature requests) ===[Apache related]=== 47061 Open User not logged under Apache ===[Apache2 related]== 44083 Open virtual() not outputting results if zlib.output_compression = On ===[Arrays related]=== 35277 Suspended incorrect recursion detection 41758 Assigned SORT_LOCALE_STRING broken for sort() in PHP6 43109 Open array_intersect() emits unexpected no of notices when 2d array is passed as arg 48478 Open Super-globals cannot be accessed with literal keys ===[COM related]== 45836 Open cannot use com ===[Compile Failure]== 42606 Open unicode/constants.c relies on ICU draft api 44502 Suspended Compiling ok with MySQL 5.0 49421 Open Make failure with MySQL 6 and PHP 6.0-dev 50101 Open [PATCH] - Avoid name clash between global and local variable 50237 Open [PATCH] - Enable correct behaviour when building PHP6 with Sun's compilers ===[Date/time related] 46948 Assigned ext/date/lib/parse_tz.c:99: Memory leak: buffer ===[Filesystem function related]== 42110 Open fgetcsv doesn't handle ""\n correctly in multiline csv record 44034 Open FILE_IGNORE_NEW_LINES in FILE does not work as expected when lines end in \r\n 46688 Open Return values differ from 5.3 and are also inconsistent 46689 Open Downcoded notices suggest unfinished code in file system? 46990 Assigned Passing UTF8 strings to filesystem functions produce wrong filenames 49479 Open move_uploaded_file is dead ===[GD related]=== 34992 Assigned imageconvolution does not respect alpha 43899 Assigned Problem in displaying right to left connected languages (like persian, arabic) ===[HTTP related]= 49273 Open setcookie() segfaults the php process when adding a positive expires value ===[I18N and L10N related] 42471 Open locale_set_default returns true on invalid locales ===[ICONV related] 48538 Open iconv_strlen() does not reject invalid charset on PHP6 ===[mcrypt related]=== 46834 Assigned Range of mcrypt functions fail on PHP 6.0 ===[MySQL related] 44076 Assigned mysql_result returns nothing with blob ===[ODBC related]= 39756 Open [PATCH] Crashes in fetching resultsets with LONG ASCII columns from MaxDB ===[OpenSSL related]== 25614 Assigned openssl_pkey_get_public() fails when given a private key ===[PDO related]== 35368 Suspended PDO query does not work properly with serialize 49270 Open configure fails if PHP source folder path contains spaces 50420 Open pdo_sqlite.so: undefined symbol: sqlite3_libversion 50818 Open SQLSTATE[HY093]: Invalid parameter number: parameter was not defined ===[Performance problem]== 50157 Open [patch] Replace !strlen(...) with !*... 50238 Analyzed [PATCH] - Using #defines to improve the performance of the TSRMG macro 50436 Open [PATCH] - Improving multi-threaded performance by propagating TSRMLS_C ===[PostgreSQL related]=== 48265 Open Source and result of database have different encodings. ===[Program Execution] 39992 Open proc_terminate() leaves children of child running 43784 Assigned escapeshellarg removes % from given string ===[Reproducible crash]=== 45107 Open setting ext_dir to "./" (and other ini settings) causes apache crash ===[Scripting Engine problem]= 47154 Open Object properties unset after setting. 49945 Open Array in multipart/form-data ===[Session related]== 44860 Open session_encode() fails for php_binary serializer ===[SimpleXML related] 48601 Open xpath() returns FALSE for legitimate query ===[
