Yes but you can't build for apache2 without building threaded and I
Of course you can. That depends on MPM apache is using.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 24, 2007, at 01:08:50, Rasmus Lerdorf wrote:
BuildSmart wrote:
On Aug 23, 2007, at 22:31:37, Rasmus Lerdorf wrote:
BuildSmart wrote:
True but by enabling it (or I thought) I could generate a single
set of
modules that could be used wit
On Thursday 23 August 2007, Stanislav Malyshev wrote:
> > define_ns('FOOBAR', $value);
>
> Can be, but there's two downsides:
> 1. define_ns would be weird construct - it would be combined
> function/operator
> 2. operators with underscores look bad...
> --
> Stanislav Malyshev, Zend Software Archi
BuildSmart wrote:
>
> On Aug 23, 2007, at 22:31:37, Rasmus Lerdorf wrote:
>
>> BuildSmart wrote:
>>> True but by enabling it (or I thought) I could generate a single set of
>>> modules that could be used with apache 1 and apache 2 but it doesn't
>>> seem to matter to the apache 1 sapi, if I build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:53:17, Ilia Alshanetsky wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-Aug-07, at 9:49 PM, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 22:31:37, Rasmus Lerdorf wrote:
BuildSmart wrote:
True but by enabling it (or I thought) I could generate a single
set of
modules that could be used with apache 1 and apache 2 but it doesn't
seem to matter to the apache 1 sap
BuildSmart wrote:
> True but by enabling it (or I thought) I could generate a single set of
> modules that could be used with apache 1 and apache 2 but it doesn't
> seem to matter to the apache 1 sapi, if I build the modules under apache
> 1 and force flat_namespace most of the modules seem to work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:53:17, Ilia Alshanetsky wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-Aug-07, at 9:49 PM, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-Aug-07, at 9:49 PM, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote:
The link in the previous e-mail was wrong, the correct location of
the tarball is:
http://downloa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote:
The link in the previous e-mail was wrong, the correct location of
the tarball is:
http://downloads.php.net/ilia/php-5.2.4RC3.tar.bz2 (md5sum:
72371ec077dd393f0c7d6370d115dcb6)
On 23-Aug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 17:05:06, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 16:50:02, Johannes Schlüter wrote:
Hi,
On Thu, 2007-08-23 at 16:23 -0400, BuildS
The link in the previous e-mail was wrong, the correct location of
the tarball is:
http://downloads.php.net/ilia/php-5.2.4RC3.tar.bz2 (md5sum:
72371ec077dd393f0c7d6370d115dcb6)
On 23-Aug-07, at 8:22 PM, Ilia Alshanetsky wrote:
Only a week has passed and we are up to RC3 already, only 5 ne
Only a week has passed and we are up to RC3 already, only 5 new fixes
since last RC one which addresses a minor security issue, which I
wanted to resolve before the final release. The source tarball can be
found at the URL below and Win32 binaries will be available shortly.
http://downloads
define_ns('FOOBAR', $value);
Can be, but there's two downsides:
1. define_ns would be weird construct - it would be combined
function/operator
2. operators with underscores look bad...
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN:
Stanislav Malyshev wrote:
>>
>> define(__NAMESPACE__.'::FOOBAR', $value) will work out of the box.
>
> Yep, works, but looks not so nice either. I have an idea: add an
> operator which prepends __NAMESPACE__.'::'. I.e. say we name if
> ns_fullname (I know, this name sucks, get me better one :), so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2007, at 16:50:02, Johannes Schlüter wrote:
Hi,
On Thu, 2007-08-23 at 16:23 -0400, BuildSmart wrote:
[...]
Symbol not found: _compiler_globals
Referenced from: /usr/local/php/lib/php/
On Thu, 2007-08-23 at 13:30 -0700, Stanislav Malyshev wrote:
> > Special FUNCTION to do "__NAMESPACE__.'::'?!
> > Sheesh..
>
> Operator, not function.
I don't think it's worth having an additional operator. const will work
for much stuff, and the rest should imo do fine with that
__NAMESPACE__.':
Hi,
On Thu, 2007-08-23 at 16:23 -0400, BuildSmart wrote:
[...]
> Symbol not found: _compiler_globals
>Referenced from: /usr/local/php/lib/php/extensions/no-debug-non-
> zts-20060613/bcompiler
>Expected in: dynamic lookup
[...]
This simply means that your PHP was built using a thread-safe
Special FUNCTION to do "__NAMESPACE__.'::'?!
Sheesh..
Operator, not function.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It appears that several modules/extensions don't work when built as
loadable extensions.
All software was built on Apple servers using the Apple Developer
Environment, I have tried the builds on owned machines running
current OSes with the sam
On 23.08.2007 23:56, Stanislav Malyshev wrote:
define(__NAMESPACE__.'::FOOBAR', $value) will work out of the box.
Yep, works, but looks not so nice either. I have an idea: add an
operator which prepends __NAMESPACE__.'::'.
Special FUNCTION to do "__NAMESPACE__.'::'?!
Sheesh..
I.e. say we
define(__NAMESPACE__.'::FOOBAR', $value) will work out of the box.
Yep, works, but looks not so nice either. I have an idea: add an
operator which prepends __NAMESPACE__.'::'. I.e. say we name if
ns_fullname (I know, this name sucks, get me better one :), so you'd say:
define(ns_fullname('F
Hi,
Here is a patch I am submitting to fix bug #42396 (PHP 5).
The problem: when PHP is configured with the '--enable-zend-multibyte' option,
it tries to autodetect unicode-encoded scripts. Then, if a script contains null
bytes after an __halt_compiler() directive, it will be considered as UTF-
We also can extend define() with additional argument that will allow to
create namespace constant.
function define(string $var, mixed $val, bool namespace_constant = false);
That'd be hard - in runtime, you don't have namespace name. So either we
should make define() an operator, or pass names
Hi - I've writing a few tests for the math extension and have a question
about floating point precision.
Here's a small example:
--TEST--
Test return type and value for expected input sin()
--INI--
precision = 14
--FILE--
--EXPECT--
sin 360 = float(-2.4492127076448E-16)
Is it right to test fo
Hi,
On Thu, 2007-08-23 at 13:46 +0400, Dmitry Stogov wrote:
> I think we must cut the patch to use only "compile-time" constants in
> namespaces.
> For runtime constants we can use existing define().
>
> This will fix inconsistency.
I think that would be good.
> We also can extend define() with
On 23.08.2007 13:46, Dmitry Stogov wrote:
I think we must cut the patch to use only "compile-time" constants in
namespaces.
For runtime constants we can use existing define().
This will fix inconsistency.
We also can extend define() with additional argument that will allow to
create namespace
I think we must cut the patch to use only "compile-time" constants in
namespaces.
For runtime constants we can use existing define().
This will fix inconsistency.
We also can extend define() with additional argument that will allow to
create namespace constant.
function define(string $var, mixe
28 matches
Mail list logo
