[PHP-DEV] Re: Updates to the QA pages

2008-02-09 Thread Edward Z. Yang
zoe wrote: > Feedback welcome! Some minor grammar picks: > though all the tests currently written are NOT in there Try: "though not all the tests currently written are in there" > more - although - these Inappropriate use of dashes: use commas, although in this case, the comma after although i

RE: [PHP-DEV] Location in php's source for ini-values

2008-02-09 Thread ehl lhe
phew, I just took a look into 5.3.0, as you mentioned, it really seems like light-years away from 5.2.5 - I have no idea where to start nor what to do, the logs in the package say that it requires several months to finish the todo-stuff, so it seems to be hopeless 1. to wait 2. to try to get in

RE: [PHP-DEV] Location in php's source for ini-values

2008-02-09 Thread ehl lhe
== = I've run into the same thing in the past, ended up moving to virtual machines in order = to circumvent ... BUT ... I found something which can apparently work in this particular = case. have a google for 'mod_macro' ... from what I read it will do what you want and it'll = save you hav

[PHP-DEV] Updates to the QA pages

2008-02-09 Thread zoe
Hi all Rob Nicholson and I have made a set updates the QA pages, mainly based on things that we've learned over the past year of test case writing - we had a lot of input from Raghu and Marcus on this too of course. The updated pages are here for review: http://zapt.info/phpt/write-test.php.

[PHP-DEV] Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2(PHP_5_3) / zend_API.c

2008-02-09 Thread Steph Fox
Hi Marcus, It's not a real problem to break the win32 build because it's a very simple fix, but it'd still be kinda nice if the PHP_5_3 checkout would just build without manual assistance. Snaps would work an' everything. Please fix last_scope declaration, mini-patch attached. - Steph -

[PHP-DEV] [RFC] Conditional INI support

2008-02-09 Thread Marcus Boerger
Hello PHPlers, attached is a patch against 5.3 that brings three feature additions to INI parsing. 1) Ternary support for values setting = ${value?1:2} If ${value} evaluates to true then setting becomes 1 otherwise 2. This cannot be nested and only works for values, not for setting names.

Re: [PHP-DEV] [patch] expose PHP version details as constants

2008-02-09 Thread Pierre Joye
Hi Marcus, On Feb 9, 2008 2:39 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote: > Hello Pierre, > yeah nice idea. I am wondering if you might want to add the cvs tag, too? > E.g.: PHP_TAG = 'PHP_5_3' Oh right, nice idea :) It would be nice to have it as well. The idea is to ease the tests writing

Re: [PHP-DEV] [patch] expose PHP version details as constants

2008-02-09 Thread Marcus Boerger
Hello Pierre, yeah nice idea. I am wondering if you might want to add the cvs tag, too? E.g.: PHP_TAG = 'PHP_5_3' marcus Friday, February 8, 2008, 1:52:27 PM, you wrote: > Hi, > Testing the PHP version can be much easier and faster if the versions > details were exposed via the constants, lik