Hi All
We are having a problem compiling PHP 5.2.3 under win32.
Building PHP on Win32 using VS2005 following the instructions at
http://hu2.php.net/manual/en/install.windows.building.php the build fails
unless libxml support is disabled.
If it is configured as
cscript /nologo configure.js --en
Hi Zoe,
Zoe Slattery wrote:
Has anyone built PHP6 using Visual C++ Express Edition V8? The
symptoms I get are pretty well described in
http://bugs.php.net/bug.php?id=39130 and I'm just wondering if this
was fixed for PHP5 and not PHP6?
Other than a slew of warnings, it built fine for me the ot
During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
what exactly was the reasoning behind adding something like
"unicode.semantics" option. Derick didn't remember, neither did I.
Apparently it's another one of these "register_globals" or
"magic_quotes_*" directives we'll remove i
I have to agree, I think giving the ability to toggle Unicode support is
going to add more confusion and grief for application developers,
especially with it being PHP_INI_SYSTEM.
The reason for the option as far I can remember was to do with
performance when you were working with binary strings,
Hi Jani,
On 6/14/07, Jani Taskinen <[EMAIL PROTECTED]> wrote:
During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
what exactly was the reasoning behind adding something like
"unicode.semantics" option. Derick didn't remember, neither did I.
Apparently it's another one of these
On Thu, 14 Jun 2007, Pierre wrote:
> Hi Jani,
>
> On 6/14/07, Jani Taskinen <[EMAIL PROTECTED]> wrote:
> > During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
> > what exactly was the reasoning behind adding something like
> > "unicode.semantics" option. Derick didn't remember,
On 6/14/07, Derick Rethans <[EMAIL PROTECTED]> wrote:
On Thu, 14 Jun 2007, Pierre wrote:
> Hi Jani,
>
> On 6/14/07, Jani Taskinen <[EMAIL PROTECTED]> wrote:
> > During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
> > what exactly was the reasoning behind adding something like
>
Hi Rob
Other than a slew of warnings, it built fine for me the other day with
VS 2005. What version of the SDK are you using as I wonder if that
might play a part in it?
Was your VS 2005 the Express Edition (ie the free one)? I downloaded the
platform SDK yesterday at the same time as I got the
Jani Taskinen wrote:
> During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
> what exactly was the reasoning behind adding something like
> "unicode.semantics" option. Derick didn't remember, neither did I.
>
> Apparently it's another one of these "register_globals" or
> "magic_qu
>> During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
>> what exactly was the reasoning behind adding something like
>> "unicode.semantics" option. Derick didn't remember, neither did I.
>>
>> Apparently it's another one of these "register_globals" or
>> "magic_quotes_*" directiv
Hi Zoe,
On 6/14/07, Zoe Slattery <[EMAIL PROTECTED]> wrote:
Hi Rob
> Other than a slew of warnings, it built fine for me the other day with
> VS 2005. What version of the SDK are you using as I wonder if that
> might play a part in it?
Was your VS 2005 the Express Edition (ie the free one)? I do
On 6/14/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
Jani Taskinen wrote:
> During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
> what exactly was the reasoning behind adding something like
> "unicode.semantics" option. Derick didn't remember, neither did I.
>
> Apparently it's
Hi Jani,
On Thu, 2007-06-14 at 16:53 +0300, Jani Taskinen wrote:
> During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
> what exactly was the reasoning behind adding something like
> "unicode.semantics" option. Derick didn't remember, neither did I.
The reason was to "keep BC"
Pierre wrote:
> On 6/14/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
>> Jani Taskinen wrote:
>> > During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
>> > what exactly was the reasoning behind adding something like
>> > "unicode.semantics" option. Derick didn't remember, neither
Johannes Schlüter wrote:
> - This feature doesn't bring BC - there will still be enough BC
> breaks.
Name one, please. The idea is that there shouldn't be any, so if you
have found one, please file a bug.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Has anyone built PHP6 using Visual C++ Express Edition V8? The symptoms
I get are pretty well described in http://bugs.php.net/bug.php?id=39130
and I'm just wondering if this was fixed for PHP5 and not PHP6?
Ah, this is a very familiar issue, you need to set USE_32BIT_TIME_T in
either project
Hi Rasmus,
On 6/14/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> As a side note, we had the same thoughts about php5, it did not work.
Not really. Nothing in PHP 5 was designed to break compatibility with
PHP 4.
In theory, I agree with you here, we were very careful about BC.
However in p
I mean, if PHP 6 is about unicode, why upgrade to PHP 6 and disable it?
To get late static binding and namespaces, of course ;)
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: ht
--- Begin Message ---
AFAIK, neither exist (yet?) in PHP 6..
(I might have missed some commits while I was awol in A-stan :)
--Jani
Stanislav Malyshev kirjoitti:
I mean, if PHP 6 is about unicode, why upgrade to PHP 6 and disable it?
To get late static binding and namespaces, of course ;)
--- Begin Message ---
Rasmus Lerdorf kirjoitti:
Johannes Schlüter wrote:
- This feature doesn't bring BC - there will still be enough BC
breaks.
Name one, please. The idea is that there shouldn't be any, so if you
have found one, please file a bug.
Some might say removing register_global
Stanislav Malyshev wrote:
Has anyone built PHP6 using Visual C++ Express Edition V8? The
symptoms I get are pretty well described in
http://bugs.php.net/bug.php?id=39130 and I'm just wondering if this
was fixed for PHP5 and not PHP6?
Ah, this is a very familiar issue, you need to set USE_32BI
>>> - This feature doesn't bring BC - there will still be enough BC
>>> breaks.
>>
>> Name one, please. The idea is that there shouldn't be any, so if you
>> have found one, please file a bug.
>
> Some might say removing register_globals, magic_quotes_*, etc. are BC
> break.
If code is portable
On 6/14/07, Jani Taskinen <[EMAIL PROTECTED]> wrote:
I mean, if PHP 6 is about unicode, why upgrade to PHP 6 and disable it?
I think if unicode.semantics remains PHP_INI_SYSTEM it is useless as
most users ( people that runs in shared hosting servers) will simple
not be able to turn it on, as w
Cristian Rodriguez wrote:
> On 6/14/07, Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
>> I mean, if PHP 6 is about unicode, why upgrade to PHP 6 and disable it?
>
> I think if unicode.semantics remains PHP_INI_SYSTEM it is useless as
> most users ( people that runs in shared hosting servers) will si
24 matches
Mail list logo
