Re: [PHP-DEV] RFC: ext/mysql deprecation

On 11/17/2012 08:54 PM, Adam Harvey wrote: On 16/11/2012 8:58 PM, "Patrick ALLAERT" wrote: 2012/11/12 Adam Harvey : Hi everyone, I've written an RFC to cover deprecating ext/mysql in PHP 5.5: https://wiki.php.net/rfc/mysql_deprecation. While we handled the soft deprecation in the documentatio

Re: [PHP-DEV] RFC: ext/mysql deprecation

On 19 November 2012 17:10, Chad Emrys wrote: > On 11/17/2012 08:54 PM, Adam Harvey wrote: >> >> On 16/11/2012 8:58 PM, "Patrick ALLAERT" wrote: >>> Maybe it is worth mentioning in the RFC what the E_DEPRECATED notice >>> message would look like so that people hiding it know what the plan >>> is.

Re: [PHP-DEV] RFC: ext/mysql deprecation

Adam, My intention at this stage is to call a vote next Monday: it feels > like the discussion has mostly died down now (which isn't to say I > think we're at a consensus necessarily — it just feels as though the > flurry of opinions have been made and argued either way), and I'm > hoping that eve

Re: [PHP-DEV] RFC: ext/mysql deprecation

hi Anthony, On Mon, Nov 19, 2012 at 1:44 PM, Anthony Ferrara wrote: > Adam, > > My intention at this stage is to call a vote next Monday: it feels >> like the discussion has mostly died down now (which isn't to say I >> think we're at a consensus necessarily — it just feels as though the >> flurr

Re: [PHP-DEV] RFC: ext/mysql deprecation

Pierre, Hard/soft deprecated? > > I suppose by "soft" you mean not actually deprecated but only > documented as such? > Correct. Hard = raising E_DEPRECATED from code. Soft = Documentation and PR only...

Re: [PHP-DEV] RFC: ext/mysql deprecation

On Sat, 2012-11-17 at 16:19 +0100, Ángel González wrote: > What are those benefits that mean everyone needs to move to mysqli? > I was making myself the opposite question :) With ext/mysql you, for instance, can not - use stored procedures (there's no "mysql_next_result" or such) - use SSL wit

Re: [PHP-DEV] Functions for getting long / double from zval with casts

On Mon, Nov 19, 2012 at 5:09 AM, Stas Malyshev wrote: > Hi! > > > Hi internals! > > > > It happens quite often that you need to extract an integer from a zval > and > > you also want it to work for integers in strings, etc. In order to do so > > you currently have to cast the zval to integer. This

Re: [PHP-DEV] [RFC] Property Accessors v1.2 Consensus Changes

On Mon, Nov 19, 2012 at 1:19 AM, Clint Priest wrote: > Can anyone who has an interest in this project please review over the > "Current Consensus Changes" section of this document: > > https://wiki.php.net/rfc/**propertygetsetsyntax-as-** > implemented/change-requests

Re: [PHP-DEV] [RFC] Property Accessors v1.2 : Internal Accessor Method Visibility / Callability

On Wed, Nov 14, 2012 at 5:24 PM, Patrick Schaaf wrote: > I thought I'd made a proposal that would solve that problem, but maybe it > was > overlooked, or more likely too ugly to be recognized as such. > > Requires a single new feature / syntax, that at least I find missing right > now: > > class

Re: [PHP-DEV] RFC: ext/mysql deprecation

On Mon, Nov 19, 2012 at 5:04 AM, Anthony Ferrara wrote: > Pierre, > > Hard/soft deprecated? > > > > I suppose by "soft" you mean not actually deprecated but only > > documented as such? > > > > Correct. Hard = raising E_DEPRECATED from code. Soft = Documentation and PR > only... > By "NEXT" are y

Re: [PHP-DEV] RFC: ext/mysql deprecation

Kris, By "NEXT" are you referring to 6.0 or 5.6? > Whatever the release after 5.5 is. Be it 5.6, or 6.0, NEXT indicates the next temporal release... > Also, can you add an option for raising E_DEPRECATED in 5.5 then removing > support altogether in 6? > That's already in there. That's what I

Re: [PHP-DEV] RFC: ext/mysql deprecation

On Mon, Nov 19, 2012 at 10:22 AM, Anthony Ferrara wrote: > And in either case, removal would happen one release after hard > deprecation. I'd actually propose that it is removed in PHP 6, even if there is PHP 5.6 and 5.7, etc. Something can be deprecated for several versions. It is a significant

Re: [PHP-DEV] [RFC] Property Accessors v1.2 : Internal Accessor Method Visibility / Callability

Am 19.11.2012 16:41 schrieb "Nikita Popov" : > > On Wed, Nov 14, 2012 at 5:24 PM, Patrick Schaaf wrote: > >> class ... { >> no methodname(); >>// or >> no $property; >> } >> > Removing methods from an extending class is an LSP violation. I see LSP as a best practise for class design, not

Re: [PHP-DEV] RFC: ext/mysql deprecation

On Mon, Nov 19, 2012 at 9:49 AM, Levi Morrison wrote: > On Mon, Nov 19, 2012 at 10:22 AM, Anthony Ferrara > wrote: > > And in either case, removal would happen one release after hard > > deprecation. > > I'd actually propose that it is removed in PHP 6, even if there is PHP > 5.6 and 5.7, etc. So