2010/8/19 Sebastian Bergmann :
> Performance optimizations, especially major ones like the ones you
> mention, should be treated the same as new features: they should not be
> introduced in a minor version.
+ Most of such changes breaks ABI, which also is against our policies.
--
regards,
Sebastian Bergmann wrote:
Can we bring the strings/hash table optimizations to PHP 5.3.x please?
Performance optimizations, especially major ones like the ones you
mention, should be treated the same as new features: they should not be
introduced in a minor version.
Give some of the thin
Am 19.08.2010 01:32, schrieb steve:
> Can we bring the strings/hash table optimizations to PHP 5.3.x please?
Performance optimizations, especially major ones like the ones you
mention, should be treated the same as new features: they should not be
introduced in a minor version.
--
Sebastian B
> With Traits, interned strings/hash table optimizations, array deref.,
Can we bring the strings/hash table optimizations to PHP 5.3.x please?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue Aug 10 07:42 PM, Josh Davis wrote:
> Derick's point was about consistency. The approach described in his
> mail is consistent with current syntax and mechanism(s). Current
> typehints do not apply any kind of conversion, so treating scalar
> hints the same way is consistent with the curre
Sascha,
Does this mean @group authorizes use of "NoPHP" as a name for a
derivative PHP version (gotta ask according to the license) ? ;-)
On Tue, Aug 10, 2010 at 7:04 PM, Sascha Schumann wrote:
>> They aren't hints. It is strict typing and in its current form I would
>> ask you guys not to call
On 11 August 2010 02:13, Arvids Godjuks wrote:
> Remember the main PHP principle? KISS. So keep it, blody hell, simple!
Please try to realize that what you find simple may not appear as
simple to everybody else. To me, typechecking is very simple: if type
equals typehint then ok else error. Very
On 11 August 2010 01:50, Stas Malyshev wrote:
> Hi!
>
>> Derick's point was about consistency. The approach described in his
>> mail is consistent with current syntax and mechanism(s). Current
>
> No it is not. There's no functions that produce errors when fed 1 instead of
> boolean "true" - all i
Yes, I understand the point of his post. But as you know - the perfect
world and the real world rearly meat together.
Just read the prevoius themes - majority was on the typecasting hints
for the primitive types. We even layed the rules quite in detail.
The thing is it will be pain in the ass to us
Hi!
Derick's point was about consistency. The approach described in his
mail is consistent with current syntax and mechanism(s). Current
No it is not. There's no functions that produce errors when fed 1
instead of boolean "true" - all internal functions convert.
typehints do not apply any
Derick's point was about consistency. The approach described in his
mail is consistent with current syntax and mechanism(s). Current
typehints do not apply any kind of conversion, so treating scalar
hints the same way is consistent with the current mechanism.
Reusing the typecasting syntax for typ
> They aren't hints. It is strict typing and in its current form I would
> ask you guys not to call the 5.4 release PHP. Because it won't be.
Fully agreed.
I'd suggest "NoPHP". "AntiPHP" might also work.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
Well, the thing is objects and arrays are complex types, so you can't
pass anything exept array to an array type hint, it just dosen't make
sence. Not everything can be converted to array and vice-versa. Same
with objects - every object is it's own type.
But the primitive types behave differently.
On Aug 10, 2010, at 3:11 PM, Johannes Schlüter wrote:
> On Wed, 2010-08-11 at 00:03 +0200, Kalle Sommer Nielsen wrote:
>> type hinting
>
> For the record: I consider the current implementation as (one of) the
> biggest mistakes in the last ten years.
>
> johannes
I'm happy to see a more strict
Hi!
For the record: I consider the current implementation as (one of) the
biggest mistakes in the last ten years.
I agree completely. The fact that obvious absence of consensus is
ignored and we are releasing feature that clearly has no consensus
behind it as a part of an official release -
Hi!
With Traits, interned strings/hash table optimizations, array deref.,
type hinting, and more we both (me and Derick) belive we are ready for
Please do not call strict typing "type hinting".
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
On 8/10/10 3:30 PM, Brian Moon wrote:
>> 2010/8/11 Johannes Schlüter:
>>> On Wed, 2010-08-11 at 00:03 +0200, Kalle Sommer Nielsen wrote:
type hinting
>>>
>>> For the record: I consider the current implementation as (one of) the
>>> biggest mistakes in the last ten years.
>
> Is there a summar
On Wed, 11 Aug 2010, Johannes Schlüter wrote:
> On Wed, 2010-08-11 at 00:03 +0200, Kalle Sommer Nielsen wrote:
> > type hinting
>
> For the record: I consider the current implementation as (one of) the
> biggest mistakes in the last ten years.
I will try to sum up my view point once more:
1. ri
2010/8/11 Johannes Schlüter:
On Wed, 2010-08-11 at 00:03 +0200, Kalle Sommer Nielsen wrote:
type hinting
For the record: I consider the current implementation as (one of) the
biggest mistakes in the last ten years.
Is there a summary of what we ended up with? I got so tired of all the
compl
Total thumbs up on that.
http://schlueters.de/blog/archives/139-Scalar-type-hints-in-PHP-trunk.html
just tells it all. A total epic fail.
2010/8/11 Johannes Schlüter :
> On Wed, 2010-08-11 at 00:03 +0200, Kalle Sommer Nielsen wrote:
>> type hinting
>
> For the record: I consider the current implem
On Wed, 2010-08-11 at 00:03 +0200, Kalle Sommer Nielsen wrote:
> type hinting
For the record: I consider the current implementation as (one of) the
biggest mistakes in the last ten years.
johannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.ne
Greetings hackers
I spoke with Derick today, and we both agreed on releasing an alpha of
PHP 5.4 to show the public what we have been working since 5.3. We are
going to release an alpha at september 2nd, which meaning packaging is
going to happen on 1st September (SVN tag, Windows binaries, etc.)
22 matches
Mail list logo
