On Aug 25, 2012, at 17:24, "Guillaume Rossolini" wrote:
> What you say is true, versions get old. But as Lester pointed out, they
> work. that is why some computer systems that have been outdated for years
> are still functioning today. It is hard to make a case for rewriting code
> that already
Hi,
On Sat, Aug 25, 2012 at 8:05 PM, Thomas Hruska wrote:
> Good businesses plan ahead and integrate upgrade expenditures into their
> cost models.
... And they also tend to avoid unnecessary costs at all costs, and that of
course means they don't upgrade unless a) absolutely necessary or b) th
Am 26.08.2012 01:57, schrieb Ferenc Kovacs:
> So you are saying that your (teams) IDE doesn't tell you the method
> signature which contains also the default values?
> I guess that the fact that many of the php core functions have
optional
> arguments and non null default
>
>
> > So you are saying that your (teams) IDE doesn't tell you the method
> > signature which contains also the default values?
> > I guess that the fact that many of the php core functions have optional
> > arguments and non null defaults must be really a PITA for you.
>
> I think what he was al
On 26/08/2012, at 4:09 AM, Ferenc Kovacs wrote:
> 2012.08.25. 19:50, "Sebastian Krebs" ezt írta:
>>
>> Am 25.08.2012 18:38, schrieb Ferenc Kovacs:
>>
>>>
>>>would this trigger a notice if $foo is not defined?
>>>if yes, then it would be different from the current behavior of
On 08/25/2012 12:59 PM, Ángel González wrote:
> I see. Thank you very much.
> Even worse, HTML5 doesn't seem to have any provision for that, as it works
> with characters. A user agent would have to protect himself from this by
> making
> those kind of utf-8 characters a hard error instead of tryin
Hi,
2012/8/26 Ángel González :
> Even worse, HTML5 doesn't seem to have any provision for that, as it works
> with characters. A user agent would have to protect himself from this by
> making
> those kind of utf-8 characters a hard error instead of trying to recover
> from it.
Right. I would like
2012/8/26 Ferenc Kovacs :
>
>
> On Sat, Aug 25, 2012 at 4:47 AM, Yasuo Ohgaki wrote:
>>
>> Hi,
>>
>> I was willing to add collision detection to session module
>> after session adoption patch is merged.
>>
>> What's the status of session adoption patch?
>> I've created patches for all 3 versions a
On 25/08/12 00:50, Rasmus Lerdorf wrote:
> In 8859-1 no chars are invalid so anything that doesn't get encoded will
> get passed through as-is. For example the byte 0xE0 is a perfectly valid
> 8859-1 character (à), but if the page is actually UTF-8 then this
> becomes the first byte of a 3-byte UTF
Am 25.08.2012 01:53, schrieb Nikita Popov:
On Sat, Aug 25, 2012 at 1:49 AM, Sebastian Krebs wrote:
Hi,
It's like with any other compound operator: A _real_ reason isn't there. But
saying "It's not worth it" is something I can live with (even if I don't
know how much effort it would take ;)). I
2012.08.25. 19:50, "Sebastian Krebs" ezt írta:
>
> Am 25.08.2012 18:38, schrieb Ferenc Kovacs:
>
>>
>> would this trigger a notice if $foo is not defined?
>> if yes, then it would be different from the current behavior of
the
>> ternary operator.
>>
>>
>> Couldn't belie
On 8/25/2012 9:11 AM, Lester Caine wrote:
Andrew Faulds wrote:
Personally I have to live with real life, and just want to help
change that
situation.
Me too. My code relies on out-of-date extensions and PHP features,
which is why
I'm *refactoring* and *rewriting* the parts which do.
Exactly w
Am 25.08.2012 18:38, schrieb Ferenc Kovacs:
would this trigger a notice if $foo is not defined?
if yes, then it would be different from the current behavior of the
ternary operator.
Couldn't believe it, thus I tested it myself
snip
Don't know, what you are ta
On 08/25/2012 10:07 AM, Lester Caine wrote:
> Rasmus Lerdorf wrote:
>>> Andrew Faulds wrote:
> >>>Personally I have to live with real life, and just want to help
> >>>change that
> >>>situation.
>>Me too. My code relies on out-of-date extensions and PHP features,
>>which is wh
Rasmus Lerdorf wrote:
Andrew Faulds wrote:
>>>Personally I have to live with real life, and just want to help
>>>change that
>>>situation.
>>Me too. My code relies on out-of-date extensions and PHP features,
>>which is why
>>I'm*refactoring* and*rewriting* the parts which do.
>
>Exactly what
On Sat, Aug 25, 2012 at 4:47 AM, Yasuo Ohgaki wrote:
> Hi,
>
> I was willing to add collision detection to session module
> after session adoption patch is merged.
>
> What's the status of session adoption patch?
> I've created patches for all 3 versions and I think Stats
> is going to merge it t
On 08/25/2012 09:11 AM, Lester Caine wrote:
> Andrew Faulds wrote:
>>> Personally I have to live with real life, and just want to help
>>> change that
>>> situation.
>> Me too. My code relies on out-of-date extensions and PHP features,
>> which is why
>> I'm *refactoring* and *rewriting* the parts
>
>
>> would this trigger a notice if $foo is not defined?
>> if yes, then it would be different from the current behavior of the
>> ternary operator.
>>
>
> Couldn't believe it, thus I tested it myself
>
snip
> Don't know, what you are talking about, but the notice _is_ the current
> behaiour a
Andrew Faulds wrote:
Personally I have to live with real life, and just want to help change that
situation.
Me too. My code relies on out-of-date extensions and PHP features, which is why
I'm *refactoring* and *rewriting* the parts which do.
Exactly what I've been doing for the last year ... I
Hi internals!
I think the generators RFC has been discussed thoroughly enough by
now, so I opened the vote:
https://wiki.php.net/rfc/generators#vote
Thanks,
Nikita
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 25/08/12 14:44, Lester Caine wrote:
Andrew Faulds wrote:
ISPs should have moved to 5.3 long ago. If they haven't, that isn't
our problem.
I'll just refer you to
http://w3techs.com/technologies/details/pl-php/5/all
5.3 is NOT being used because of the changes it introduced, and
distributions
Andrew Faulds wrote:
ISPs should have moved to 5.3 long ago. If they haven't, that isn't our problem.
I'll just refer you to
http://w3techs.com/technologies/details/pl-php/5/all
5.3 is NOT being used because of the changes it introduced, and distributions do
NOT yet include 5.4 as the norm
Pers
On 25/08/12 14:27, Lester Caine wrote:
Andrew Faulds wrote:
OK Lester, you've whined enough, what do you want us to do? Freeze
development
for 5 years so ISPs can slowly catch up, or something?
Simply taking care to provide fixed point that we can work to would
have helped. LTS versions have
Andrew Faulds wrote:
OK Lester, you've whined enough, what do you want us to do? Freeze development
for 5 years so ISPs can slowly catch up, or something?
Simply taking care to provide fixed point that we can work to would have helped.
LTS versions have been rejected in the past, but PLEASE ca
On 25/08/12 13:33, Laruence wrote:
Hi:
Voting closed.
Result:
foreach supports list syntax: 11 for yes, 4 for no. accepted.
foreach supports list with silent token: 2 for yes, 10 for no. denied.
thanks for your great advise.
I will commit the patch later.
thanks
Hi:
Voting closed.
Result:
foreach supports list syntax: 11 for yes, 4 for no. accepted.
foreach supports list with silent token: 2 for yes, 10 for no. denied.
thanks for your great advise.
I will commit the patch later.
thanks
On Sat, Aug 18, 2012 at 12:34 PM, Laruence
On 25.08.2012, at 11:15, Lester Caine wrote:
> Many of my 'problems' with all of the 'progress' being made with PHP are
> caused because I'm using a core framework who's origins go back to PHP4 days.
I'm sorry, but what is the point of this email? This is a mailing list, not a
group therapy se
On 25/08/12 13:08, Lester Caine wrote:
Marco Pivetta wrote:
Just wanted to remind you that the latest Smarty 2.x version is
2.6.26, released
in the middle of 2009...
And our own version of Smarty2 has been maintained and updated several
times in the intervening period. It's a lot easier to fix
Marco Pivetta wrote:
Just wanted to remind you that the latest Smarty 2.x version is 2.6.26, released
in the middle of 2009...
And our own version of Smarty2 has been maintained and updated several times in
the intervening period. It's a lot easier to fix security holes as they are
identified t
Ferenc Kovacs wrote:
So what do you propose?
There always will be people who don't want any new fearure or improvement but
their code workinf forever without any investment(refactoring) on their part.
We shouldn't stop the development for that alone.
If I were them, I would pick an enterprise dis
Heya,
Just wanted to remind you that the latest Smarty 2.x version is 2.6.26,
released in the middle of 2009...
3 years have passed by, and change is something that cannot really be
stopped. You can either freeze the environment and plan to re-build your
projects or maintain them, applying change a
FYI, there is already namespace support in the extension, and you can also
use type hinting on the pointcuts with interfaces/traits besides class
names.
2012.08.25. 11:16, "Lester Caine" ezt írta:
>
> Many of my 'problems' with all of the 'progress' being made with PHP are
caused because I'm using a core framework who's origins go back to PHP4
days. Many of the facilities are currently unusable simply because they
have not had any of the PHP5.2/3/
Many of my 'problems' with all of the 'progress' being made with PHP are caused
because I'm using a core framework who's origins go back to PHP4 days. Many of
the facilities are currently unusable simply because they have not had any of
the PHP5.2/3/4 changes applied while all the stuff that is
Hi,
I'm +1 for having internal/input/output/script encoding setting at PHP
or Zend level.
If the default is the problem is the problem, we should set default_charset
default to UTF-8 and use them as default for internal/input/output/script
and functions that affected by encoding.
When XSS adviso
2012.08.25. 9:24, "Kris Craig" ezt írta:
>
> Hey guys,
>
> I'm not sure whom to ask, but could somebody with the appropriate privs
add
> a "Quick Fix" to the Bugs dropdown that says something along the lines of,
> "Support for this PHP version has been discontinued (won't fix)"? There's
> current
Hey guys,
I'm not sure whom to ask, but could somebody with the appropriate privs add
a "Quick Fix" to the Bugs dropdown that says something along the lines of,
"Support for this PHP version has been discontinued (won't fix)"? There's
currently a similar one already but it's specific to PHP 4, an
37 matches
Mail list logo
