Daniel Convissor | 1 Oct 05:16 2008

Re: [PHP-DEV] solving the namespace conflict issues betweenfunction/staticmethod class constant/ns constant

On Tue, Sep 30, 2008 at 07:51:04AM +0200, Lukas Kahwe Smith wrote:
> On 30.09.2008, at 05:36, Daniel Convissor wrote:
>
> I linked to one tally (not sure if its the final one) in my recent  
> email:
> http://marc.info/?l=php-internals&m=113313170231815&w=2

Thanks.

>> Regardless of whether we use the same separator between
>> namespaces and the elements or if we just use a different separator
>> between namespaces and the elements, some separator needs to change.

> But yes, we I presume what you mean to say is that if we want  
> to improve the situation we have to find a second separator.

Yeah.  I didn't express myself clearly. :)

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
            data intensive web and database programming
                http://www.AnalysisAndSolutions.com/
 4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

(Continue reading)

Vesselin Kenashkov | 1 Oct 09:34 2008
Picon

Re: [PHP-DEV] namespace issues

I'm -1 for "removing constants and functions from the namespaces". As I
wrote already in another thread, is it possible to have a fatal error thrown
when the engine detects an ambiguity situation? Are there any logical (i
mean from OOP point of view) or internals (performance and so on) problems
with this solution? In my opinion is better than dropping funcs & consts.

Vesselin Kenashkov

On Mon, Sep 22, 2008 at 10:45 PM, Stanislav Malyshev <stas <at> zend.com> wrote:

> Hi!
>
> On the ZendCon, we (Marcus, Elizabeth, Andi and myself) had a talk about
> what we'd like to do with namespaces, and we arrived at the following
> conclusions, which we propose to implement in 5.3:
>
> 1. Allow braces for namespaces. So, the syntax for namespaces will be:
> a) namespace foo;
> should be first (non-comment) statement in the file, namespace extends to
> the end of the file or next namespace declaration.
> b) namespace foo {}
> can appear anywhere on the top scope (can not be nested).
> Mixing both syntaxes in one file is not possible. The semantics of both
> syntaxes will be identical.
>
> 2. Simplify resolution order for classes in the namespace: unqualified
> names are resolved this way:
> a) check "use" list if the name was defined at "use", follow that
> resolution
> b) if not, the name resolves to namespace::name
(Continue reading)

Lukas Kahwe Smith | 1 Oct 09:52 2008

Re: [PHP-DEV] __getStatic


On 08.09.2008, at 11:23, Timm Friebe wrote:

> Hi,
>
> [...__(set|get|unset|isset)static()...]
>>> Patch looks pretty good. Plaease add __issetStatic and   
>>> __unsetStatic. Then provide tests and submit to HEAD. For 5.3  
>>> Lukas and Johannes have to agree but I am sure they first want to  
>>> see it in HEAD.
>>
>> Hope we havent missed any other we need to make this stuff  
>> complete ..
>> But here is the blessing of the two RM's to have this committed  
>> before the alpha2 release ..
>
> I've updated the patch and added some tests with it.
>
> http://sitten-polizei.de/php/getstatic.diff
>
> This requires a zend_vm_gen.php as I needed a new opcode  
> (ZEND_ASSIGN_CLASS, 137). Please review this patch carefully,  
> especially the part in zend_vm_def.h, I'm not sure this is correct.

Can someone review this patch?

regards,
Lukas Kahwe Smith
mls <at> pooteeweet.org

(Continue reading)

Игорь | 1 Oct 12:43 2008

[PHP-DEV] Выкуп авто. Дорого.

Выкупаю битые и горелые автомобили отечественного и
иностранного производства в любом состоянии,
а также целые, требующие срочного выкупа в день обращения.

Оценка. Эвакуатор.           

8 (915) 134-53-30. Алексей.          

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Gregory Beaver | 1 Oct 14:59 2008
Picon

Re: [PHP-DEV] namespace issues

Vesselin Kenashkov wrote:
> I'm -1 for "removing constants and functions from the namespaces". As I
> wrote already in another thread, is it possible to have a fatal error thrown
> when the engine detects an ambiguity situation? Are there any logical (i
> mean from OOP point of view) or internals (performance and so on) problems
> with this solution? In my opinion is better than dropping funcs & consts.

Hi,

There are problems with the internal implementation.  For instance,
constants do not store the line number on which they were created, and
are not actually registered as existing until runtime, so conflict
checks would happen at runtime.  This would mean your application could
work perfectly until a rarely executed branch of code is accessed and
boom, fatal error.

Greg

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Dmitry Stogov | 1 Oct 15:15 2008

Re: [PHP-DEV] ext/soap and http header

Hi Brain,

A little bit different patch committed into PHP_5_3 and HEAD.
I don't think it's allowed to commit it into PHP_5_2.
Please verify, if it works for you.

Thanks. Dmitry.

Brian J. France wrote:
> After some more testing I needed to tweak the patch and the example,
> here is version 2.
> 
>  $opts = array('http' => array('header' => 'X-foo: bar'));
>  $ctx = stream_context_create($opts);
> 
> Brian
> 
> 
> --- ext/soap/php_http.c.orig    2008-09-26 05:39:50.000000000 -0700
> +++ ext/soap/php_http.c    2008-09-26 06:42:34.000000000 -0700
>  -391,7 +391,8  <at>  <at> 
>      PG(allow_url_fopen) = old_allow_url_fopen;
> 
>      if (stream) {
> -        zval **cookies, **login, **password;
> +        php_stream_context *context = NULL;
> +        zval **cookies, **login, **password, **tmpzval = NULL;
>        int ret = zend_list_insert(phpurl, le_url);
> 
>          add_property_resource(this_ptr, "httpurl", ret);
(Continue reading)

Hannes Magnusson | 1 Oct 15:39 2008
Picon

[DOC] Commit messages dead?

Hi all

It looks like [DOC] has failed miserably, it is of no use if only few
people use it for few commits.
Adding to the fact there is almost no activity in the documentations
we really need to find a better way to organize things.
Currently we have [DOC], (closed) bug reports, NEWS and wiki all
overlapping with each other.. not very attractive for newcomers.

Does anyone have any idea how we can organize things better and get
more people to document?

-Hannes

---------- Forwarded message ----------
From: Dmitry Stogov <dmitry <at> php.net>
Date: Wed, Oct 1, 2008 at 15:13
Subject: [PHP-CVS] cvs: php-src(PHP_5_3) / NEWS  /ext/soap php_http.c
To: php-cvs <at> lists.php.net

dmitry          Wed Oct  1 13:13:34 2008 UTC

 Modified files:              (Branch: PHP_5_3)
   /php-src    NEWS
   /php-src/ext/soap   php_http.c
 Log:
 Added ability to send user defined HTTP headers with SOAP request.

Thiago H. Pojda | 1 Oct 16:07 2008
Picon

[PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?

On Wed, Oct 1, 2008 at 10:39 AM, Hannes Magnusson <
hannes.magnusson <at> gmail.com> wrote:

> Hi all
>
> It looks like [DOC] has failed miserably, it is of no use if only few
> people use it for few commits.
> Adding to the fact there is almost no activity in the documentations
> we really need to find a better way to organize things.
> Currently we have [DOC], (closed) bug reports, NEWS and wiki all
> overlapping with each other.. not very attractive for newcomers.
>
> Does anyone have any idea how we can organize things better and get
> more people to document?
>
> -Hannes
>

Well,

Not sure how things were around here as I'm kinda new with docs but I might
have something.

I don't how it works internally neither how it works for new documentation.
But I've seen how Ubuntu Launchpad eases the work for translators. Have you
seen it? An online interface is much more attractive than this CVS thing.

Many of us - 'documentors' -  (if not all) are programmers and used to use
CVS and other versioning system. But this takes some extra time that IMHO it
shouldn't. If you want to "spread the word" and get lots of people to help
(Continue reading)

Derick Rethans | 1 Oct 18:33 2008
Picon
Picon

Re: [PHP-DEV] solving the namespace conflict issues between function/static method class constant/ns constant

On Fri, 19 Sep 2008, Greg Beaver wrote:

> Hi all,
> 
> There is a problem in the namespace implementation.  This code demonstrates
> the issue:
> 
> code.inc:
> <?php
> namespace foo;
> class test {
> const my = 1;
> static function bar(){}
> }
> 
> namespace foo::test;
> const my = 2;
> function bar(){}
> ?>
> 
> main.php:
> <?php
> include 'code.inc';
> foo::test::bar(); // always calls namespace function
> call_user_func(array('foo::test', 'bar')); // the only way to call static
> method
> echo foo::test::my; // always 2
> $a = new foo::test;
> echo $a::my; // the only way to access foo::test::my
> ?>
(Continue reading)

Jochem Maas | 1 Oct 18:56 2008

Re: [PHP-DEV] solving the namespace conflict issues between function/static method class constant/ns constant

Derick Rethans schreef:
> On Fri, 19 Sep 2008, Greg Beaver wrote:
> 
>> Hi all,
>>
>> There is a problem in the namespace implementation.  This code demonstrates
>> the issue:
>>
>> code.inc:
>> <?php
>> namespace foo;
>> class test {
>> const my = 1;
>> static function bar(){}
>> }
>>
>> namespace foo::test;
>> const my = 2;
>> function bar(){}
>> ?>
>>
>> main.php:
>> <?php
>> include 'code.inc';
>> foo::test::bar(); // always calls namespace function
>> call_user_func(array('foo::test', 'bar')); // the only way to call static
>> method
>> echo foo::test::my; // always 2
>> $a = new foo::test;
>> echo $a::my; // the only way to access foo::test::my
(Continue reading)


Gmane