Hannes Magnusson wrote:
On Sun, Jun 1, 2008 at 7:43 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
Hi!
use FooBar::In::Some::NameSpace as foo,
SomeOther::Cool:Massive::awesome::space as bar, And::other:namespace
as foobar;
vs
use FooBar::In::Some::NameSpace as foo;
use SomeOther::Cool:Massi
On Mon, Jun 2, 2008 at 2:26 AM, Lars Strojny <[EMAIL PROTECTED]> wrote:
> Hi Pierre,
>
> Am Montag, den 02.06.2008, 01:02 +0200 schrieb Pierre Joye:
> [...]
>> While working on the windows ports, I asked Sara about the mhash
>> status in regard of the new shiny ext/hash. The plan is to remove
>> ex
Hi Pierre,
Am Montag, den 02.06.2008, 01:02 +0200 schrieb Pierre Joye:
[...]
> While working on the windows ports, I asked Sara about the mhash
> status in regard of the new shiny ext/hash. The plan is to remove
> ext/hash completely and emulate it in ext/hash to keep the BC. It
You mean
Hi,
While working on the windows ports, I asked Sara about the mhash
status in regard of the new shiny ext/hash. The plan is to remove
ext/hash completely and emulate it in ext/hash to keep the BC. It
could even a configuration flag if one likes to be sure to clean his
code to use only the hash AP
On Sun, Jun 1, 2008 at 7:43 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> use FooBar::In::Some::NameSpace as foo,
>> SomeOther::Cool:Massive::awesome::space as bar, And::other:namespace
>> as foobar;
>> vs
>> use FooBar::In::Some::NameSpace as foo;
>> use SomeOther::Cool:Massive::awe
Lars Strojny wrote:
>> Not like they will be listened to unless they are "commiters".
>
> They are heard. The issue is, as always in programming, you want to do
[...]
> maintainability, safety and security. I'm not saying the core
> contributors are always right, but there being core contributo
Edward Z. Yang wrote:
> My proposal is to introduce a new filter (for the filter extension)
> which performs codepoint sanitization appropriate for HTML/XML contexts
> (alternatively, this could be an option on the FILTER_DEFAULT filter,
> which would be for Unicode strings, I assume). This filter
> From: Stanislav Malyshev wrote:
> Hi!
>
> Attached is the patch that implements multiple elements in use
> statement, like this:
>
> use foo::bar as baz, foo::baz as bazbaz;
>
> Any objections to it?
A very nice addition. I have use for this.
Two thumbs up. :)
Best Regards
Mike Robinson
-
Hi!
use FooBar::In::Some::NameSpace as foo,
SomeOther::Cool:Massive::awesome::space as bar, And::other:namespace
as foobar;
vs
use FooBar::In::Some::NameSpace as foo;
use SomeOther::Cool:Massive::awesome::space as bar;
use And::other:namespace as foobar;
Well, with (im)proper formatting many t
On Sun, Jun 1, 2008 at 7:11 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> I find the whole namespace issue complicated enough as it is.
>> "importing" multiple namespaces and "aliasing" various
>> classess/functions all in one line decreases the readability imo.
>
> I must say I fail
Hi!
I find the whole namespace issue complicated enough as it is.
"importing" multiple namespaces and "aliasing" various
classess/functions all in one line decreases the readability imo.
I must say I fail to understand how it's decreasing readability. Is
function foo($a, $b, $c) hard to read?
On Sun, Jun 1, 2008 at 6:09 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
> Attached is the patch that implements multiple elements in use statement,
> like this:
>
> use foo::bar as baz, foo::baz as bazbaz;
>
> Any objections to it?
Yes.
I find the whole namespace issue complicated e
Hi
Looks pretty good to me, I would prefer to have that insted of multiple use
statements after each other like you can do with the global keyword.
"+1" from me
Kalle
- Original Message -
From: "Stanislav Malyshev" <[EMAIL PROTECTED]>
To: "'PHP Internals'"
Sent: Sunday, June 01, 2008
Applied to 5_3 and head.
Scott
Pierre Joye wrote:
On Sun, Jun 1, 2008 at 3:01 PM, Gregory Beaver <[EMAIL PROTECTED]> wrote:
Pierre Joye wrote:
hi Greg,
Please commit it, thanks for the patch!
Someone with ZendEngine2 karma will need to commit.
Scott will do it asap.
Cheers,
--
PHP In
Hi!
Attached is the patch that implements multiple elements in use
statement, like this:
use foo::bar as baz, foo::baz as bazbaz;
Any objections to it?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
Index: zend_la
Okay after looking at the php source looks like the problem is in
php_request_shutdown where it flushes all the buffers.
So I'm trying from my extension to register a shutdown function to be
called prior to that(only alternative I see other than mucking the php
source).
I've figured out basi
> Creating library Release_TS\php6apache.lib and object
> Release_TS\php6apache.exp
> mod_php.obj : error LNK2001: unresolved external symbol [EMAIL PROTECTED]
> Release_TS\php6apache.dll : fatal error LNK1120: 1 unresolved externals
>
> SAPI sapi\apache build complete
>
> btw, thought i'd check P
>
>
> You're right about the filename, so I corrected config.w32. Though I'm not
> sure about the "unresolved external" part from your next message, so we'll
> wait for someone with more experience than me in that area I guess. :-)
Thanks Matt!
Regards
Marco
Hi Marco,
- Original Message -
From: "Marco"
Sent: Sunday, June 01, 2008
> I've done some quick checks and I think part of the problem is in the
> following commit
>
>
http://cvs.php.net/viewvc.cgi/php-src/sapi/apache2handler/config.w32?r1=1.4&r2=1.5
>
> AFAICS mod_php5.c has been renamed
Hi Pierre
> Can you open a bug report please? One of the windows guys (me or
> other) will try to fix this as soon as possible.
Thanks, bug reported at http://bugs.php.net/bug.php?id=45144
>
> Thanks for the head up!
Thanks for the quick response!
Regards
Marco
Hi,
On Sun, Jun 1, 2008 at 3:57 PM, Marco <[EMAIL PROTECTED]> wrote:
>> mod_php.obj : error LNK2001: unresolved external symbol [EMAIL PROTECTED]
>> Release_TS\php6apache.dll : fatal error LNK1120: 1 unresolved externals
>> SAPI sapi\apache build complete
>>
>>
> I think this part was broken with
> mod_php.obj : error LNK2001: unresolved external symbol [EMAIL PROTECTED]
> Release_TS\php6apache.dll : fatal error LNK1120: 1 unresolved externals
> SAPI sapi\apache build complete
>
>
I think this part was broken with
http://cvs.php.net/viewvc.cgi/php-src/sapi/apache/mod_php.c?r1=1.6&r2=1.7
I
I've done some quick checks and I think part of the problem is in the
following commit
http://cvs.php.net/viewvc.cgi/php-src/sapi/apache2handler/config.w32?r1=1.4&r2=1.5
AFAICS mod_php5.c has been renamed mod_php.c in PHP6.
Regards
Marco
Hi All
I have downloaded the snapshot build of PHP6 from snaps.php.net but noticed
the building of the apache extensions are failing.
According to the log I can see the following 3 problems
Creating library Release_TS\php6apache.lib and object Release_TS\php6apache.exp
mod_php.obj : error LNK200
On Sun, Jun 1, 2008 at 3:01 PM, Gregory Beaver <[EMAIL PROTECTED]> wrote:
> Pierre Joye wrote:
>> hi Greg,
>>
>> Please commit it, thanks for the patch!
>>
>>
> Someone with ZendEngine2 karma will need to commit.
Scott will do it asap.
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd
Pierre Joye wrote:
> hi Greg,
>
> Please commit it, thanks for the patch!
>
>
Someone with ZendEngine2 karma will need to commit.
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
hi Greg,
Please commit it, thanks for the patch!
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Derick Rethans wrote:
On Wed, 21 May 2008, Steph Fox wrote:
I looked into it again (and found things I didn't know before). This one's
bugging me enough that I braved the Wiki:
http://wiki.php.net/rfc/calltimebyref
I don't think we should get rid of it, or add a notice/message/whatever.
Bec
28 matches
Mail list logo
