Kris Craig wrote:
Either way, our common goal here is to get people to stop using ext/mysql now so
that we can trash it when the time comes. And as far as that goes, I think that
what happened with magic_quotes and Drupal is a perfect example of how
deprecation can effectively push devs to act w
Hi,
Slightly related topic.
I recently looked into new output code in PHP 5.4.
It's MUCH nicer than older code. Good job!
However, new code encapsulate output globals. (I mean internally)
It would be nice for my extension if output globals are exposed.
Exposing output global is not mandatory, tho
On 29 November 2012 00:36, Anthony Ferrara wrote:
> However, I'd like to ask you to do something else here. Can you please
> update the RFC to reflect the discussions that happened on list? Not
> everything that was talked about, but the major discussion points at least.
> That way it's there for
Kris,
I disagree. Whether we're deprecating an extension or a subset of
> functions, the practical impact is pretty much the same. As for moving it
> to PECL, why are we even discussing that here? It's completely outside the
> scope of this RFC. I imagine moving it to PECL would make the most
> Kris,
>
> There was no "ext/magic_quotes" that was retired to PECL. You're comparing
> apples with oranges.
>
> David
>
>
I disagree. Whether we're deprecating an extension or a subset of
functions, the practical impact is pretty much the same. As for moving it
to PECL, why are we even discussi
On 29/11/12 07:33, Kris Craig wrote:
On Wed, Nov 28, 2012 at 8:43 AM, Anthony Ferrara wrote:
Patrick,
Sorry, but removing the E_DEPRECATED notice when moved to PECL is not
part of the proposed RFC and should certainly not happen.
The proposal doesn't actually propose anything about a move
On 29/11/12 10:11, Mailing list wrote:
.. annoying top posting...
This is getting close to a good solution.
ini option mysql_is_deprecated - can not be set in .ini/htaccess etc,
only by ini_set() - so hosters/distros can not fix it...
Normally added just before mysql_connect...
ini_set('my
On 28/11/2012 23:11, Mailing list wrote:
> - Users will get warnings on upgrading - it can not be hidden by
> hosters/distros etc.
Think you might be wildly underestimating the ability of both distros
and stuff like cPanel to patch the extension. Then again - I think
everybody might be.
--
PHP I
2012/11/28 Adam Harvey :
> At this stage, I intend to close the vote in a week's time: so
> Wednesday, December 5.
+1 for deprecation in 5.5
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.
.. annoying top posting...
This is getting close to a good solution.
ini option mysql_is_deprecated - can not be set in .ini/htaccess etc,
only by ini_set() - so hosters/distros can not fix it...
Normally added just before mysql_connect...
ini_set('mysql_is_deprecated', "I WILL NOT USE IT I
On 29/11/12 05:09, Ángel González wrote:
I see it as simple to show E_DEPRECATED but not when installed from PECL.
1) Add a
int mysql_extension_triggers_deprecated_warning = 1;
And use it as a conditional for triggering the warning.
2) Copy the extension code to PECL
3) Add these changes in P
On Wed, Nov 28, 2012 at 8:43 AM, Anthony Ferrara wrote:
> Patrick,
>
>
> Sorry, but removing the E_DEPRECATED notice when moved to PECL is not
> > part of the proposed RFC and should certainly not happen.
> >
>
> The proposal doesn't actually propose anything about a move to PECL. It's
> listed in
On 26/11/12 22:21, Sara Golemon wrote:
> https://wiki.php.net/rfc/request-tempnam
>
> Just a bit of hand-holding for those who don't remember to clean up
> their messes.
I like it.
Also note that it's not always that people “don't
remember to clean up their messes” since there are
several tricky ca
I see it as simple to show E_DEPRECATED but not when installed from PECL.
1) Add a
int mysql_extension_triggers_deprecated_warning = 1;
And use it as a conditional for triggering the warning.
2) Copy the extension code to PECL
3) Add these changes in PECL
- If the mysql functions are not alread
Patrick,
Sorry, but removing the E_DEPRECATED notice when moved to PECL is not
> part of the proposed RFC and should certainly not happen.
>
The proposal doesn't actually propose anything about a move to PECL. It's
listed in the "possible future actions" section exactly once. But the RFC
doesn't
Adam,
Thanks for opening voting.
However, I'd like to ask you to do something else here. Can you please
update the RFC to reflect the discussions that happened on list? Not
everything that was talked about, but the major discussion points at least.
That way it's there for future reference, and pe
From: Patrick ALLAERT
Sorry, but removing the E_DEPRECATED notice when moved to PECL is not part
of the proposed RFC and should certainly not happen.
I don't get what is the reason behind it?
Yes, the extension is old but it still works perfectly fine and even
outperforms the newer mysqli/pd
Patrick ALLAERT wrote:
2012/11/28 Lester Caine:
>There is no 'objection' to deprecating the extension, but adding
>E_DEPRECATED to the code is problematic since that should NOT be present in
>a PECL version of the code?
Sorry, but removing the E_DEPRECATED notice when moved to PECL is not
part
thanks. :)
On Wed, Nov 28, 2012 at 4:58 PM, Ivan Enderlin @ Hoa <
ivan.ender...@hoa-project.net> wrote:
> Oh, and also :
>
> s/ calcualated/calculated/
> s/extended_vallue/extended_**value/
>
> (always in the UPGRADING file).
>
> :-)
>
>
>
>
> On 28/11/12 11:57, Dmitry Stogov wrote:
>
>> Hi
>>
>>
2012/11/28 Lester Caine :
> There is no 'objection' to deprecating the extension, but adding
> E_DEPRECATED to the code is problematic since that should NOT be present in
> a PECL version of the code?
Sorry, but removing the E_DEPRECATED notice when moved to PECL is not
part of the proposed RFC an
On Wed, Nov 28, 2012 at 11:30 AM, Philip Olson wrote:
> The idea of moving it to PECL is not represented in the vote. But
> it's something to consider as it's a real possibility. It could
> both symbolize that we are serious about not using ext/mysql, and
> considering most Linux distros would si
Oh, and also :
s/ calcualated/calculated/
s/extended_vallue/extended_value/
(always in the UPGRADING file).
:-)
On 28/11/12 11:57, Dmitry Stogov wrote:
Hi
I've tried to review the generators related changes made in PHP-5.5 and
improve them from both consistency and performance points of vi
Hi Dmitry,
s/ informatin/information
in the UPGRADING file.
Best regards.
On 28/11/12 11:57, Dmitry Stogov wrote:
Hi
I've tried to review the generators related changes made in PHP-5.5 and
improve them from both consistency and performance points of view.
The patch also makes a small performa
Hi
I've tried to review the generators related changes made in PHP-5.5 and
improve them from both consistency and performance points of view.
The patch also makes a small performance improvement to PHP-5.5 in general,
however, it changes some ZE internals that can be used by
some extension (e.g. X
On Nov 28, 2012, at 2:08 AM, Pierre Joye wrote:
> hi,
>
> On Wed, Nov 28, 2012 at 10:55 AM, Alexey Zakhlestin
> wrote:
>> I voted "no", "(b)"
>> We should mention deprecation in manual as hard as possible, we should
>> mention it in ext/mysql/config.m4 and any other place we can reach.
>> Then
hi,
On Wed, Nov 28, 2012 at 10:55 AM, Alexey Zakhlestin wrote:
> I voted "no", "(b)"
> We should mention deprecation in manual as hard as possible, we should
> mention it in ext/mysql/config.m4 and any other place we can reach.
> Then, at some point (I'm fine with 5.6, but 6.0 would do also), we
I voted "no", "(b)"
We should mention deprecation in manual as hard as possible, we should
mention it in ext/mysql/config.m4 and any other place we can reach.
Then, at some point (I'm fine with 5.6, but 6.0 would do also), we
should just move it to PECL, without using E_DEPRECATED
--
Alexey Zakhle
Adam Harvey wrote:
Deprecation is a strong signal. It's a signal that it's time to update
tutorials. It's a signal to schedule upgrades for code when new
versions are written to use more modern APIs. It's a signal to those
of us who speak at conferences, and help people in various fora and
variou
28 matches
Mail list logo
