Lukas Kahwe Smith wrote:
Pierre wrote:
Also, is it not George S, Ilia and Wez that are listed as mainters of
PDO_MYSQL?
Yes, as they do all the initial work. What's the point? Mysql was not
a maintainer/initiator of any of the .net db layers (or any other
language).
I will try to discuss
On 9/24/07, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
Ok, it seems that MySQL AB is finally committing to fix up PDO_MySQL and
to generally accept the fact that PDO is the future. Of course mysqli
will also be actively maintained. But they will also make mysqlnd play
nicely with PDO etc.
Those are very welcome news indeed. I look forward to participation
of MySQL AB folks in the PDO development.
On 24-Sep-07, at 7:31 AM, Lukas Kahwe Smith wrote:
Lukas Kahwe Smith wrote:
Pierre wrote:
Also, is it not George S, Ilia and Wez that are listed as
mainters of
PDO_MYSQL?
Yes,
On Sun, 16 Sep 2007, Ilia Alshanetsky wrote:
On 16-Sep-07, at 1:02 PM, Steph Fox wrote:
Mmm... but that means dictating which features can or can't go into
an extension or a specific build system purely on the level of
outside interest in them.
Steph, isn't the goal of core to
Hi Lester,
On 9/17/07, Lester Caine [EMAIL PROTECTED] wrote:
( And I'd still like to know what use the code for mysqlind is for those of us
who will never enable mysql ? )
Only ext/mysql and ext/mysqli use it. PDO is somehow planed but I
have serious doubts about the motivations of mysql to
Hey all,
On 9/17/07, Stanislav Malyshev [EMAIL PROTECTED] wrote:
So while I think making list and voting is great, I think we shouldn't
replace good old per-case consideration and discussion with arithmetics.
If we have clear winners and losers, it's fine, but in between we still
need to hear
David Wang wrote:
My personal opinion is that it is ready for 5.3 and should be put into
5.3. It is stable, end-users will not be affected unless they want to
use it, extension writers should not even be affected, there is no
performance degradation and it would help make PHP a much more
Pierre skrev:
Only ext/mysql and ext/mysqli use it. PDO is somehow planed but I
have serious doubts about the motivations of mysql to ever support pdo
like they support other generic connectors (see .net...).
The first posts on the net from MySQL-people talked about mysqli first,
PDO second
On 9/17/07, Keryx Web [EMAIL PROTECTED] wrote:
Pierre skrev:
Only ext/mysql and ext/mysqli use it. PDO is somehow planed but I
have serious doubts about the motivations of mysql to ever support pdo
like they support other generic connectors (see .net...).
The first posts on the net from
Pierre wrote:
Also, is it not George S, Ilia and Wez that are listed as mainters of
PDO_MYSQL?
Yes, as they do all the initial work. What's the point? Mysql was not
a maintainer/initiator of any of the .net db layers (or any other
language).
I will try to discuss this and get a commitment
Ilia Alshanetsky wrote:
On 15-Sep-07, at 7:18 PM, Stanislav Malyshev wrote:
NP ;-) Btw the detailed breakdown of the votes is available here
http://bb.prohost.org/53Features.pdf
I have taken the data from this PDF and slightly reworked things [1] so
that its easy to see which topics got
On 16-Sep-07, at 11:02 AM, Lukas Kahwe Smith wrote:
Ilia Alshanetsky wrote:
On 15-Sep-07, at 7:18 PM, Stanislav Malyshev wrote:
NP ;-) Btw the detailed breakdown of the votes is available here
http://bb.prohost.org/53Features.pdf
I have taken the data from this PDF and slightly reworked
.
- Steph
- Original Message -
From: Ilia Alshanetsky [EMAIL PROTECTED]
To: Lukas Kahwe Smith [EMAIL PROTECTED]
Cc: Stanislav Malyshev [EMAIL PROTECTED]; PHP Developers Mailing List
internals@lists.php.net
Sent: Sunday, September 16, 2007 4:31 PM
Subject: Re: [PHP-DEV] PHP 5.3
Alshanetsky [EMAIL PROTECTED]
To: Lukas Kahwe Smith [EMAIL PROTECTED]
Cc: Stanislav Malyshev [EMAIL PROTECTED]; PHP Developers Mailing List
internals@lists.php.net
Sent: Sunday, September 16, 2007 4:31 PM
Subject: Re: [PHP-DEV] PHP 5.3 Suggested Feature List (Summary)
On 16-Sep-07, at 11:02
On 16-Sep-07, at 1:02 PM, Steph Fox wrote:
Mmm... but that means dictating which features can or can't go into
an extension or a specific build system purely on the level of
outside interest in them.
Steph, isn't the goal of core to contain things that are of common
use and are not for
Hi Ilia,
Mmm... but that means dictating which features can or can't go into an
extension or a specific build system purely on the level of outside
interest in them.
Steph, isn't the goal of core to contain things that are of common use
and are not for niche uses and wouldn't lack of
- Original Message -
From: Ilia Alshanetsky [EMAIL PROTECTED]
To: Lukas Kahwe Smith [EMAIL PROTECTED]
Cc: Stanislav Malyshev [EMAIL PROTECTED]; PHP Developers Mailing List
internals@lists.php.net
Sent: Sunday, September 16, 2007 4:31 PM
Subject: Re: [PHP-DEV] PHP 5.3 Suggested Feature List (Summary
internals@lists.php.net
Sent: Sunday, September 16, 2007 5:47 PM
Subject: Re: [PHP-DEV] PHP 5.3 Suggested Feature List (Summary)
Hello Steph,
speakin as a looser - we should keep what we just decided on and do it.
Do it as in work on it. As in code. As in no more politics for the moment
Lukas has a good point about the 0 votes, however if there are niche
features most people don't really care/know about that in itself means
that there is not much support for said functionality. IMHO the point of
There's a difference. Let't take two features which got similar voting
record -
Mmm... but that means dictating which features can or can't go into an
extension or a specific build system purely on the level of outside
interest in them.
Steph, isn't the goal of core to contain things that are of common use
and are not for niche uses and wouldn't lack of interest imply
Ilia Alshanetsky wrote:
For the most part it seems that there is a general consensus on the
features to go into PHP 5.3, my suggestion is that all features with
10 points are to be put into the 5.3 TODO and the rest can have
another change for PHP 6 and/or PHP 5.4 (if that comes to pass).
Hi!
Thanks for organizing the things!
What we do wih low score ones? I think it's good to note that -1 and
+1 isn't the same as two 0's...
Will the TODO be on http://oss.backendmedia.com/PhP53?
For the most part it seems that there is a general consensus on the
features to go into PHP 5.3,
On 15-Sep-07, at 7:18 PM, Stanislav Malyshev wrote:
Hi!
Thanks for organizing the things!
NP ;-) Btw the detailed breakdown of the votes is available here
http://bb.prohost.org/53Features.pdf
What we do wih low score ones? I think it's good to note that -1
and +1 isn't the same as two
From: Stanislav Malyshev [mailto:[EMAIL PROTECTED]
14) Link phar extension from PECL into core (possibly enabling it by
default)
-1, we discussed why :) 0 if not enabled by default.
Yes, it was discussed, and I thought it was clear for everybody that phar had
to remain
in pecl and was
Hello LAUPRETRE,
to cut this short. Noone tried to overrule anyone and noone tried to
outsmart or trick in any sense either. In the past we decided on the
following. First it is to early to ring in Phar for a variety of reasons. As
development went on it was more than appropriate for the RM to
On Sun, 9 Sep 2007, Ilia Alshanetsky wrote:
1) Backport the namespaces patch for PHP 6
-1
2) Symlink the intl extension from PECL, but leave it disabled by default as
is the case with all extensions dependent on external libs
1
3) Apply the Late Static Binding Patch
1
4) Implement
Message-
From: Steph Fox [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 11, 2007 6:40 PM
To: Mike Robinson; 'Ilia Alshanetsky'; 'PHP Developers Mailing List'
Subject: Re: [PHP-DEV] PHP 5.3 Suggested Feature List
Hi Mike,
7) Introduce mysqlind library into core and use
On Mon, 2007-09-10 at 13:47 -0700, Andi Gutmans wrote:
16) Introduce new php.ini files parser/scanner + CGI/FastCGI?
htaccess style ini file support
1 0 -1
0 (this can be nice but we need to make sure it's optional because those
stat()'s can be very hard on
On Mon, 2007-09-10 at 22:56 +0200, Pierre wrote:
On 9/10/07, Andi Gutmans [EMAIL PROTECTED] wrote:
16) Introduce new php.ini files parser/scanner + CGI/FastCGI?
htaccess style ini file support
1 0 -1
0 (this can be nice but we need to make sure it's
On 9/11/07, Jani Taskinen [EMAIL PROTECTED] wrote:
On Mon, 2007-09-10 at 22:56 +0200, Pierre wrote:
On 9/10/07, Andi Gutmans [EMAIL PROTECTED] wrote:
16) Introduce new php.ini files parser/scanner + CGI/FastCGI?
htaccess style ini file support
1 0 -1
Ilia Alshanetsky wrote:
1) Backport the namespaces patch for PHP 6
0
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
0
3) Apply the Late Static Binding Patch
1
4) Implement David's Circular
That patch is a very good idea, but it does not work there are symbols
that are no lomger exported on libxml extension , and although
everything compiles, I ended with a broken PHP.
Can you give a bit more details on what is broken? Does it mean there's a
problem on Windows too, since Windows
1) Backport the namespaces patch for PHP 6
+1
3) Apply the Late Static Binding Patch
+1
6) Remove safe_mode, register_globals and magic_quotes
-1
8) OpenID enabling patch for OpenSSL and PHP 5
+1
10) Split off deprecation from E_STRICT into E_DEPRECATED
+1
11) Merge the
1) Backport the namespaces patch for PHP 6
1
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
1
3) Apply the Late Static Binding Patch
1
4) Implement David's Circular Garbage collection patch
0
If it counts for anything, here's my vote on the bits I know/care about:
2) Symlink the intl extension from PECL, but leave it disabled by default
as is the case with all extensions dependent on external libs
+1, I've a feeling this will become important later
3) Apply the Late Static
Am 09.09.2007 um 19:07 schrieb Ilia Alshanetsky:
Its been about a week since RFS for features to go into 5.3 has
gone out and while there was not a flood of ideas there is a
substantial list of key changes people would like to go into this
release. I've compiled a list of all of the
Steph Fox wrote:
18) Introduce concept of strict classes that do not permit dynamic
property creation
-1, this whole idea just sounds so weird for PHP.
Sure, but how PHPish is this fatal error?
[EMAIL PROTECTED]:~/build/php-5.2-debug$ cli -r 'class c{} c::$x=1;'
Fatal error: Access to
Heya Mike,
-1, this whole idea just sounds so weird for PHP.
Sure, but how PHPish is this fatal error?
[EMAIL PROTECTED]:~/build/php-5.2-debug$ cli -r 'class c{} c::$x=1;'
Fatal error: Access to undeclared static property: c::$x in Command
line code on line 1
The idea, as far as I
Since my vote counts for shyte, I'll humbly offer brief remarks instead.
Ilia Alshanetsky queried:
6) Remove safe_mode, register_globals and magic_quotes
1 0 -1
*Major* BC break in a minor version? Ouch. This should wait I think.
7) Introduce mysqlind library
Hi Mike,
7) Introduce mysqlind library into core and use it as a
backend for PDO and mysqli extensions (possibly enabling them
by default)
1 0 -1
The mysqlind driver is currently alpha. Wherever it goes it should be
marked
EXPERIMENTAL and off by default Frankly, I'm wondering (out loud)
On 9/9/07, Ilia Alshanetsky [EMAIL PROTECTED] wrote:
1) Backport the namespaces patch for PHP 6
1 0 -1
+1
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
1 0
Stanislav Malyshev wrote:
10) Split off deprecation from E_STRICT into E_DEPRECATED
0. Why do we *need* it again?
E_STRICT is about general coding style that we feel should be
encouraged. Its sort of the comp sci teacher in a box.
E_DEPRECATED is things we drop are replace. People that
1) Backport the namespaces patch for PHP 6
0
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
1
3) Apply the Late Static Binding Patch
1
4) Implement David's Circular Garbage collection patch
0
5)
Hi Rob,
On 9/10/07, Rob Richards [EMAIL PROTECTED] wrote:
8) OpenID enabling patch for OpenSSL and PHP 5
Which one? (from the looks you are refering to Wez's origional) I though
it was already decided a while back that the patch from Dmitry was going in.
For what we discussed, Dmitry's
Ilia Alshanetsky wrote:
1) Backport the namespaces patch for PHP 6
+1
3) Apply the Late Static Binding Patch
+1
5) Implement Sqlite3 support via the ext/sqlite extension (patch is
already available)
+1
6) Remove safe_mode, register_globals and magic_quotes
-1
7) Introduce
1) Backport the namespaces patch for PHP 6
1
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
0
3) Apply the Late Static Binding Patch
1
4) Implement David's Circular
On 9/10/07, Lester Caine [EMAIL PROTECTED] wrote:
PLEASE can we have an assessment of how this new list of features will affect
users porting from PHP4 rather than simply assuming that this is just a simple
'upgrade' from PHP5.2.X.
As discussion has already been shouted down on the vote list
Hello Ilia,
Sunday, September 9, 2007, 7:07:37 PM, you wrote:
1) Backport the namespaces patch for PHP 6
+1
2) Symlink the intl extension from PECL, but leave it disabled by
+1
3) Apply the Late Static Binding Patch
+1
4) Implement David's Circular Garbage collection patch
+1
5)
On Monday 10 September 2007 02:43:52 pm Pierre wrote:
On 9/10/07, Lester Caine [EMAIL PROTECTED] wrote:
PLEASE can we have an assessment of how this new list of features will
affect users porting from PHP4 rather than simply assuming that this is
just a simple 'upgrade' from PHP5.2.X.
Hi,
Ilia Alshanetsky wrote:
List of Feature Ideas
1) Backport the namespaces patch for PHP 6
+1
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
0
3) Apply the Late Static
Hello Ilia,
Monday, September 10, 2007, 3:08:57 PM, you wrote:
Hello Ilia,
Sunday, September 9, 2007, 7:07:37 PM, you wrote:
6) Remove safe_mode, register_globals and magic_quotes
remove register_globals only, rest for 6.*
Actually we should get E_DEPRECATED and mark all as deprecated
Lukas Kahwe Smith skrev:
Stanislav Malyshev wrote:
10) Split off deprecation from E_STRICT into E_DEPRECATED
0. Why do we *need* it again?
Without it, we mix 2 different concepts, we also make it needlessly hard
for library maintainers to leverage E_STRICT. As a result library
Without it, we mix 2 different concepts, we also make it needlessly hard
for library maintainers to leverage E_STRICT. As a result library
maintainers have the choice of either jumping to every new minor version
as the minimum requirement or more or less ignoring E_STRICT all together.
OK, I
See below:
-Original Message-
From: Ilia Alshanetsky [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 09, 2007 10:08 AM
To: PHP Developers Mailing List
Subject: [PHP-DEV] PHP 5.3 Suggested Feature List
List of Feature Ideas
1) Backport the
On 9/9/07, Ilia Alshanetsky [EMAIL PROTECTED] wrote:
12) Merge the GCC 4 -fvisibility patch
That patch is a very good idea, but it does not work there are symbols
that are no lomger exported on libxml extension , and although
everything compiles, I ended with a broken PHP.
--
On 9/10/07, Andi Gutmans [EMAIL PROTECTED] wrote:
See below:
-Original Message-
From: Ilia Alshanetsky [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 09, 2007 10:08 AM
To: PHP Developers Mailing List
Subject: [PHP-DEV] PHP 5.3 Suggested Feature List
List of Feature
Andi Gutmans wrote:
14) Link phar extension from PECL into core (possibly enabling it by
default)
10 -1
-1 (I'd prefer a standard format which can be manipulated with standard
tools (also some tests we did with TAR format we got much better
performance). In
-Original Message-
From: Pierre [mailto:[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 1:56 PM
To: Andi Gutmans
Cc: Ilia Alshanetsky; PHP Developers Mailing List
Subject: Re: [PHP-DEV] PHP 5.3 Suggested Feature List
For the record here, a cache is planed once we have a stable
Ilia Alshanetsky wrote:
List of Feature Ideas
1) Backport the namespaces patch for PHP 6
-1
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
1
3) Apply the Late Static
That patch is a very good idea, but it does not work there are symbols
that are no lomger exported on libxml extension , and although
everything compiles, I ended with a broken PHP.
Can you give a bit more details on what is broken? Does it mean there's
a problem on Windows too, since Windows
On Sunday 09 September 2007, Ilia Alshanetsky wrote:
Its been about a week since RFS for features to go into 5.3 has gone
out and while there was not a flood of ideas there is a substantial
list of key changes people would like to go into this release. I've
compiled a list of all of the
On 9/9/07, Ilia Alshanetsky [EMAIL PROTECTED] wrote:
Its been about a week since RFS for features to go into 5.3 has gone
out and while there was not a flood of ideas there is a substantial
list of key changes people would like to go into this release. I've
compiled a list of all of the
On 9/9/07, Ilia Alshanetsky [EMAIL PROTECTED] wrote:
Its been about a week since RFS for features to go into 5.3 has gone
out and while there was not a flood of ideas there is a substantial
list of key changes people would like to go into this release. I've
compiled a list of all of the
Ilia Alshanetsky wrote:
Its been about a week since RFS for features to go into 5.3 has gone out
and while there was not a flood of ideas there is a substantial list
of key changes people would like to go into this release. I've compiled
a list of all of the suggestions I've received, they are
1) Backport the namespaces patch for PHP 6
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
I haven't looked at it yet.
3) Apply the Late Static Binding Patch
+0
4) Implement David's Circular
On 09.09.2007 21:07, Ilia Alshanetsky wrote:
Its been about a week since RFS for features to go into 5.3 has gone
out and while there was not a flood of ideas there is a substantial
list of key changes people would like to go into this release. I've
compiled a list of all of the
On 9/9/07, Antony Dovgal [EMAIL PROTECTED] wrote:
On 09.09.2007 21:07, Ilia Alshanetsky wrote:
Its been about a week since RFS for features to go into 5.3 has gone
out and while there was not a flood of ideas there is a substantial
list of key changes people would like to go into this
All none listed are zero for me.
1) Backport the namespaces patch for PHP 6
1
6) Remove safe_mode, register_globals and magic_quotes
-1
7) Introduce mysqlind library into core and use it as a backend for PDO
and mysqli extensions (possibly enabling them by default)
1
8) OpenID
1) Backport the namespaces patch for PHP 6
1 as soon as we have it stabilized.
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the case with all extensions dependent on external libs
1
3) Apply the Late Static Binding Patch
1
4) Implement David's
Hi Ilia,
On Sunday 09 September 2007 07:07:37 pm Ilia Alshanetsky wrote:
List of Feature Ideas
1) Backport the namespaces patch for PHP 6
1 0 -1
+1
2) Symlink the intl extension from PECL, but leave it disabled by
default as is the
On 9 Sep 2007, at 13:07, Ilia Alshanetsky wrote:
Its been about a week since RFS for features to go into 5.3 has
gone out and while there was not a flood of ideas there is a
substantial list of key changes people would like to go into this
release. I've compiled a list of all of the
Comments inline
On Sun, 2007-09-09 at 13:07 -0400, Ilia Alshanetsky wrote:
Its been about a week since RFS for features to go into 5.3 has gone
out and while there was not a flood of ideas there is a substantial
list of key changes people would like to go into this release. I've
Scott MacVicar wrote:
6) Remove safe_mode, register_globals and magic_quotes
10-1
+1, The sooner we get rid of this the better, though I could see things
going wrong if its not properly documented for everyone. I'd perhaps not
remove the functions such as
On Monday 10 September 2007, Lester Caine wrote:
Scott MacVicar wrote:
6) Remove safe_mode, register_globals and magic_quotes
10-1
+1, The sooner we get rid of this the better, though I could see things
going wrong if its not properly documented for everyone. I'd
On 9/10/07, Larry Garfield [EMAIL PROTECTED] wrote:
On Monday 10 September 2007, Lester Caine wrote:
Scott MacVicar wrote:
6) Remove safe_mode, register_globals and magic_quotes
10-1
+1, The sooner we get rid of this the better, though I could see things
going
75 matches
Mail list logo
