On 04/30/2013 10:04 AM, Frank Liepert wrote:
> Voting starts as of now and ends on 7th May, 2013.
I voted -1; not because I do not think the feature is useful
but because I think it belongs in an extension such as Xdebug and
not in PHP itself.
--
PHP Internals - PHP Runtime Development Mailin
On Mon, May 6, 2013 at 10:55 AM, Sebastian Bergmann wrote:
> On 04/30/2013 10:04 AM, Frank Liepert wrote:
> > Voting starts as of now and ends on 7th May, 2013.
>
> I voted -1; not because I do not think the feature is useful
> but because I think it belongs in an extension such as Xdebug and
>
2013/5/6 Sebastian Bergmann :
> On 04/30/2013 10:04 AM, Frank Liepert wrote:
>> Voting starts as of now and ends on 7th May, 2013.
>
> I voted -1; not because I do not think the feature is useful
> but because I think it belongs in an extension such as Xdebug and
> not in PHP itself.
Seriously,
On Mon, May 6, 2013 at 12:31 PM, Patrick ALLAERT wrote:
> 2013/5/6 Sebastian Bergmann :
> > On 04/30/2013 10:04 AM, Frank Liepert wrote:
> >> Voting starts as of now and ends on 7th May, 2013.
> >
> > I voted -1; not because I do not think the feature is useful
> > but because I think it belongs
Hi Rasmus,
I agree with you that strings are not the best way to refer to an element
sometimes. However, to me your Symfony2 example only demonstrates the flaw
of the component's design decision, not the limitation of the language.
Sometimes developers (not just Symfony, but other frameworks too)
> -Ursprüngliche Nachricht-
> Von: Ferenc Kovacs [mailto:tyr...@gmail.com]
> Gesendet: Montag, 6. Mai 2013 12:47
> An: Patrick ALLAERT
> Cc: Sebastian Bergmann; PHP Development
> Betreff: Re: [PHP-DEV] [VOTE] Class instances counter
>
> On Mon, May 6, 2013 at 12:31 PM, Patrick ALLAERT
> wr
Seva,
I understand that you can reference properties more consistently
using "{fullClassName}::{fieldName}" notation, but it's still a string, and
although it's now almost practically safe to assume that strings formatted
in that way are property-references, it still doesn't address the problem
in
Not elegant - true, not expressive - I don't agree.
My reference to Java was not to point how things should be, but how people
find *proper* ways to overcome missing edge features of a language.
On Mon, May 6, 2013 at 12:44 PM, Rasmus Schultz wrote:
> Seva,
>
> I understand that you can refere
BTW, I didn't propose to wrap any use of a property reference into a meta
object, in this case a certain distinguishable string format could
represent it with no extra handling.
On Mon, May 6, 2013 at 12:44 PM, Rasmus Schultz wrote:
> Seva,
>
> I understand that you can reference properties mor
Well, I don't disagree as such - there's any number of (mostly bad) ways to
work around missing language features...
On Mon, May 6, 2013 at 1:12 PM, Seva Lapsha wrote:
> BTW, I didn't propose to wrap any use of a property reference into a meta
> object, in this case a certain distinguishable str
Le 04/05/2013 14:39, Laruence a écrit :
>with this patch, preg_replace_callback will call user callback with two
> arguments, the first one is the same, the second is the regex key if the
> regex is an array or NULL if the regex is a string.
Here is another example from a real case (Horde_
Hi!
> Here is another example from a real case (Horde_Date)
Looks like the case of doing it wrong. In most cases it doesn't even
need regexp, in others, generic regexp with post-parsing would probably
be more efficient as this seems to do 20+ passes through the string.
--
Stanislav Malyshev, S
12 matches
Mail list logo
