Re: [PHP-DEV] Unicode progress [Was: unicode.semantics ad infinitum]

Hi Andi, et. al, Am Montag, den 19.05.2008, 23:03 -0700 schrieb Andi Gutmans: > The idea here was to find volunteers who'd try and run their apps and > some standard apps on this so we can figure out what the migration > path looks like. That'd also give us the necessary data point to make > a dec

RE: [PHP-DEV] Unicode progress [Was: unicode.semantics ad infinitum]

The idea here was to find volunteers who'd try and run their apps and some standard apps on this so we can figure out what the migration path looks like. That'd also give us the necessary data point to make a decision on default for strings. I think none of us right now truly knows what to expec

[PHP-DEV] .NET Enabled

Pierre Joye wrote: However, the PHP Building From Source web site has indicated to download the 2005 SDK. That might be ok, but it does introduce mismatches if one is using vc6 (for whatever reason). It should be the February 2003 SDK. It is the last one known to work with VC6. It is the one

Re: [PHP-DEV] Unicode progress [Was: unicode.semantics ad infinitum]

Yes, but we should run some sort of test suite and see what exactly breaks with unicode strings as the default ones. On Mon, May 19, 2008 at 2:42 PM, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote: > > On 19.05.2008, at 23:34, Cristian Rodríguez wrote: > > Andrei Zmievski escribió: >> >>> Done. See

Re: [PHP-DEV] Unicode progress [Was: unicode.semantics ad infinitum]

On 19.05.2008, at 23:34, Cristian Rodríguez wrote: Andrei Zmievski escribió: Done. See latest commit: switch is removed and mode is defaulted to On. Thank you , VERY MUCH Andrei, now we can **really** move forward.. well the next question is binary or unicode as the default for strings

Re: [PHP-DEV] Unicode progress [Was: unicode.semantics ad infinitum]

Andrei Zmievski escribió: Done. See latest commit: switch is removed and mode is defaulted to On. Thank you , VERY MUCH Andrei, now we can **really** move forward.. -- "Progress is possible only if we train ourselves to think about programs without thinking of them as pieces of executable co

[PHP-DEV] Unicode progress [Was: unicode.semantics ad infinitum]

Done. See latest commit: switch is removed and mode is defaulted to On. -Andrei On Wed, May 14, 2008 at 5:59 AM, Steph Fox <[EMAIL PROTECTED]> wrote: > Hi all, > > Is there any chance of getting the unicode.semantics issue sorted soon? > > > >

[PHP-DEV] Dirty hands required

Hi all, I just spent forever trying to get Phar to work as expected under CVS HEAD when unicode.semantics=1. There are still 46 test failures I've no idea how to address, with stream conversion and path issues leading the way (more than half all failures) and Phar's _SERVER munging close behin

[PHP-DEV] Re: LIBXML conflict

On Mon, May 19, 2008 at 8:13 PM, Hector Santos <[EMAIL PROTECTED]> wrote: > Pierre Joye wrote: > >>> Now, of course, you might not be able to learn all this until > >>> some one (outside the inner loop) confronts these issues. >> >> The thing is that there is a golden rule on Windows and for PHP >>

[PHP-DEV] Re: LIBXML conflict

Pierre Joye wrote: Now, of course, you might not be able to learn all this until >> some one (outside the inner loop) confronts these issues. The thing is that there is a golden rule on Windows and for PHP windows: Always use the same library versions and the same compiler. For the compiler

Re: [PHP-DEV] Class Properties in Interfaces?

Hi! Would the following be acceptable? (Not E_STRICT) If error_reporting does not include E_STRICT, then I think making the language internals depend on error_reporting setting is not a very good idea, especially on E_STRICT. I.e., I have nothing against making unset() trigger E_STRICT if i

Re: [PHP-DEV] Class Properties in Interfaces?

Hello Stanislav, Monday, May 19, 2008, 2:13:14 AM, you wrote: > Hi! >> As much as I agree on the interface part, changing my sentence from >> containing 'interface' to 'protocol' makes it even a bug today. And that >> by the way was the purpose of my mail. > I think it is not right to call it a

[PHP-DEV] Advanced SOAP

Hi All This could be a silly question but one of the things that I struggle with whilst developing my applications is the lack of WSDL generation in the PHP Soap extension and the need to secure my SOAP messages using signing etc which isn't really documented on how to do in the current extension.

Re: [PHP-DEV] Class Properties in Interfaces?

Richard Quadling wrote: > In trying to understand the proposal of allowing properties via > interfaces from your (Chris') point of view, what benefit do we get? I don't use interfaces at all so I don't have a strong opinion about the benefits or drawbacks of adding properties really but ... > All

Re: [PHP-DEV] Class Properties in Interfaces?

2008/5/19 Christian Schneider <[EMAIL PROTECTED]>: > Richard Quadling wrote: >> (Not E_STRICT) If error_reporting does not include E_STRICT, then >> unset()'ting properties defined in interfaces is allowed and operates >> exactly as it does on normal variables and for properties defined in >> class

Re: [PHP-DEV] Class Properties in Interfaces?

Richard Quadling wrote: > (Not E_STRICT) If error_reporting does not include E_STRICT, then > unset()'ting properties defined in interfaces is allowed and operates > exactly as it does on normal variables and for properties defined in > classes. Whilst this may break the contract, this is what curr

[PHP-DEV] PHP 6 Bug Summary Report

PHP 6 Bug Database summary - http://bugs.php.net Num Status Summary (59 total including feature requests) ===[*Compile Issues]== 45022 Open Can't get php6 snap to ./configure on mac, fails at libxml2 ==

Re: [PHP-DEV] Class Properties in Interfaces?

2008/5/19 Stanislav Malyshev <[EMAIL PROTECTED]>: > Hi! > >> As much as I agree on the interface part, changing my sentence from >> containing 'interface' to 'protocol' makes it even a bug today. And that >> by the way was the purpose of my mail. > > I think it is not right to call it a "bug", sinc