This is indeed not possible, because strings are not class context
independent, you can pass them to anywhere. A string just doesn't know what
namespace it belongs to and this does not make sense without providing more
context in client libraries (such as docblocks).
Also the use statement informa
This is an interesting discussion, and since I use phpdoc extensively, it's an
area that I have been thinking about, but WHY do you have to make it so
difficult to follow by simply bundling more text at the top. THIS needs to be
quoted properly and THEN perhaps other people can follow the discus
On Tue, Feb 26, 2013 at 10:08 AM, Lester Caine wrote:
> This is an interesting discussion, and since I use phpdoc extensively,
> it's an area that I have been thinking about, but WHY do you have to make
> it so difficult to follow by simply bundling more text at the top. THIS
> needs to be quoted
Benjamin Eberlei wrote:
Sorry, forgot to post inline. Thanks for mentioning it and doing it wrong
yourself, made me laugh ;-) But you are right.
Actually if you check, it was quoted in the right place ;)
But it is getting VERY annoying that a few people choose to ignore the lists
requested st
hi Lester,
Please stop hijacking threads with all possible off topics and to use
uppercase to improve your arguments (or lack of).
Thanks for your understanding, take #42.
On Tue, Feb 26, 2013 at 11:01 AM, Lester Caine wrote:
> Benjamin Eberlei wrote:
>>
>> Sorry, forgot to post inline. Thanks
Pierre Joye wrote:
hi Lester,
Please stop hijacking threads with all possible off topics and to use
uppercase to improve your arguments (or lack of).
Thanks for your understanding, take #42.
Get a life, actually read the discussion and follow the list RULES
The question came up due to tr
There is also a PECL extension already under development that will
probably fill this void so many people would like to see filled.
On 2/25/2013 7:43 AM, Nils Andre wrote:
Hi Everyone on the list, I have no RFC Karma here so far, so I post this to
the list at first. There has been ongoing disc
On 2/20/2013 2:35 PM, Christopher Jones wrote:
Hi Paul,
My thesis is the other way round. More people in the community need
to become PHP core developers. This is historically how PHP
development has occurred, since nobody has idle time to adopt projects
they are not 100% behind.
Increasing
Hello Nikita,
2013/2/25 Nikita Popov
> Hi internals!
>
> PHP 5.4 added support for expressions of the kind (new Foo)->bar(), (new
> Foo)->bar and (new Foo)['bar'].
>
>
I guess it must have been discussed, but Is there any technical reason or
conflict that prevents us from having something like n
2013/2/26 Lazare Inepologlou
> Hello Nikita,
>
> 2013/2/25 Nikita Popov
>
> > Hi internals!
> >
> > PHP 5.4 added support for expressions of the kind (new Foo)->bar(), (new
> > Foo)->bar and (new Foo)['bar'].
> >
> >
> I guess it must have been discussed, but Is there any technical reason or
> c
On Tue, Feb 26, 2013 at 01:35:47PM +0100, Sebastian Krebs wrote:
> 2013/2/26 Lazare Inepologlou
>
> > Hello Nikita,
> >
> > 2013/2/25 Nikita Popov
> >
> > > Hi internals!
> > >
> > > PHP 5.4 added support for expressions of the kind (new Foo)->bar(), (new
> > > Foo)->bar and (new Foo)['bar'].
>
On Mon, Feb 25, 2013 at 2:35 AM, Pierre Joye wrote:
> While reading both PRs and features requests in bugs.php.net, I would
> like to strongly suggest to make any new proposal (new features, PRs,
> etc.), no matter how small, targeting 5.6 or later.
>
> 5.5 will go in beta soon and we have already
On Tue, Feb 26, 2013 at 7:41 AM, Dmitry Stogov wrote:
> Hi Nikita,
>
> I like the idea.
> But note, that it may cause some unexpected behaviour and bugs.
> I didn't test the patch I just guess it on my previous experience
> introducing similar features.
>
> - usage expression in write context (e.
Hello All,
Before drafting an RFC I would like to gauge interest in adding:
get_object_constants and get_class_constants
Currently this can only be done through ReflectionClass which is far slower
than retrieving them directly from the constants table. Some simple
timings show that through refle
On Tue, Feb 26, 2013 at 4:19 PM, Mike Willbanks wrote:
> Hello All,
>
> Before drafting an RFC I would like to gauge interest in adding:
> get_object_constants and get_class_constants
>
> Currently this can only be done through ReflectionClass which is far slower
> than retrieving them directly f
>> Before drafting an RFC I would like to gauge interest in adding:
>> get_object_constants and get_class_constants
>>
>> I have already drafted up a PR with the changes and supplemental data:
>> https://github.com/php/php-src/pull/292
>>
You took the time to make a PR, but not an RFC? This should
> >> Before drafting an RFC I would like to gauge interest in adding:
> >> get_object_constants and get_class_constants
> >>
> >> I have already drafted up a PR with the changes and supplemental data:
> >> https://github.com/php/php-src/pull/292
> >>
> You took the time to make a PR, but not an RFC
On Tue, Feb 26, 2013 at 7:10 PM, Nikita Popov wrote:
> On Tue, Feb 26, 2013 at 7:41 AM, Dmitry Stogov wrote:
>
>> Hi Nikita,
>>
>> I like the idea.
>> But note, that it may cause some unexpected behaviour and bugs.
>> I didn't test the patch I just guess it on my previous experience
>> introduci
On Tue, Feb 26, 2013 at 7:41 AM, Dmitry Stogov wrote:
> Hi Nikita,
>
> I like the idea.
> But note, that it may cause some unexpected behaviour and bugs.
> I didn't test the patch I just guess it on my previous experience
> introducing similar features.
>
> - usage expression in write context (e.
On Tue, Feb 26, 2013 at 8:49 PM, Nikita Popov wrote:
> On Tue, Feb 26, 2013 at 7:41 AM, Dmitry Stogov wrote:
>
>> Hi Nikita,
>>
>> I like the idea.
>> But note, that it may cause some unexpected behaviour and bugs.
>> I didn't test the patch I just guess it on my previous experience
>> introduci
Hi,
>
> Yeah. It's not a simple patch. In the past, we had a lot of problems after
> introducing foo()[$i] syntax, because some edge cases were not taken in
> account.
>
> Thanks. Dmitry.
>From what I remember, the same problem that I spotted by foo()[$i] is
the one that we already had with foo()
I'd missed the significance of the initial thread but the problems of
now documenting these sorts of 'changes' to language does need to be
addressed? HOPEFULLY without forcing 'annotation' on us when there is
I am still working on docs for this, perhaps if docs were not in SVN,
things would b
On Mon, Feb 25, 2013 at 5:14 PM, Nikita Popov wrote:
> Thoughts?
There is now more than enough materials to put in a well written RFC. Thanks :-)
--
Pierre
@pierrejoye
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
The idea from the user perspective is very simple and clear.
I really don't see what to discuss. All the questions are about
implementation and they must be solvable.
Thanks. Dmitry.
On Tue, Feb 26, 2013 at 10:04 PM, Pierre Joye wrote:
> On Mon, Feb 25, 2013 at 5:14 PM, Nikita Popov
> wrote:
>
hi,
On Tue, Feb 26, 2013 at 7:21 PM, Dmitry Stogov wrote:
> The idea from the user perspective is very simple and clear.
> I really don't see what to discuss. All the questions are about
> implementation and they must be solvable.
The idea is all the edge cases and possible issues listed so it c
Hello All,
The reference issues I previously noted were mostly about unset not being a
proper write context when the ZE is tricked into thinking it is a
reference; this is used for both write and read write but not unset.
This causes countless issues where you are unable to unset a
multi-dimensio
2013.02.26. 19:00, "Ralph Schindler" ezt írta:
>
>
>> I'd missed the significance of the initial thread but the problems of
>> now documenting these sorts of 'changes' to language does need to be
>> addressed? HOPEFULLY without forcing 'annotation' on us when there is
>
>
> I am still working on d
could you ellaborate?
I fail to see why would the choice of vcs would matter in this.
or maybe you are referring to the docbook format?
I'm just out of practice with both SVN and docbook, as such, it's more
of a chore to sit down and write/format/compile documentation than with
git/markdown.
Hi,
I just want to get a feel for whether the following idea would be instantly
rejected (for example I get the feeling that adding keywords is a big deal):
Often, when writing frameworks, you need to make public or protected
functionality or classes which should only be called from inside the
Hi!
> Before drafting an RFC I would like to gauge interest in adding:
> get_object_constants and get_class_constants
>
> Currently this can only be done through ReflectionClass which is far slower
> than retrieving them directly from the constants table. Some simple
> timings show that through
30 matches
Mail list logo
