Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65580 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 97552 invoked from network); 3 Feb 2013 19:45:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Feb 2013 19:45:02 -0000 Authentication-Results: pb1.pair.com header.from=karoly@negyesi.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=karoly@negyesi.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain negyesi.net from 209.85.128.46 cause and error) X-PHP-List-Original-Sender: karoly@negyesi.net X-Host-Fingerprint: 209.85.128.46 mail-qe0-f46.google.com Received: from [209.85.128.46] ([209.85.128.46:53699] helo=mail-qe0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 63/21-22879-C3EBE015 for ; Sun, 03 Feb 2013 14:45:00 -0500 Received: by mail-qe0-f46.google.com with SMTP id 1so2530923qec.5 for ; Sun, 03 Feb 2013 11:44:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:mime-version:in-reply-to:references:from:date :message-id:subject:cc:content-type:x-gm-message-state; bh=EdNTNs7IUHXEyovjm/WrC7KeXuN99vf9x9q7XyHQW/8=; b=mhJvqHn54u7CSKPKbPbv/c+pkUqQVBGeyzGYIkXfexPZ+1L9NQXA31zJTRYoBUaBHO ApG6yw6+E17fcFTw0lTcQLDj+AMmaKj6PBSxGkpFCGm/4vYzZdsZRlpUBLgzzLzKvk51 t7eHplpv6c3k9noK/CiJALc1OkXmLS2FT7chR4xE+UUcvd13d5QfgIPkUjpRD1WFMqAY CdE3a3CMruuIkAFcFVIV+9Pa6qWzEwUbA57JvVeOjzKffTmg+PNrYSpUUj0vLuMvFQ2l qPBKnhc8FCN56jXCs7KxMr0q9JnNHG2avu/mM5V+0t7Sa9XJlZsbytXZkjOpLjzOvJ9q BfUw== X-Received: by 10.224.111.83 with SMTP id r19mr17385194qap.39.1359920697056; Sun, 03 Feb 2013 11:44:57 -0800 (PST) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx.google.com with ESMTPS id z5sm9859740qer.8.2013.02.03.11.44.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 11:44:56 -0800 (PST) Received: by mail-qa0-f54.google.com with SMTP id hg5so1008646qab.13 for ; Sun, 03 Feb 2013 11:44:55 -0800 (PST) X-Received: by 10.229.193.134 with SMTP id du6mr4178703qcb.46.1359920695477; Sun, 03 Feb 2013 11:44:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.49.97.65 with HTTP; Sun, 3 Feb 2013 11:44:35 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Feb 2013 11:44:35 -0800 Message-ID: Cc: "internals@lists.php.net" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQk09/BdI5KudMqag0T1awuQKrd8mbWdCV5SUv8BeatHUSPf2LJWeZM8wkrMov74DQP+TF8J Subject: Re: [PHP-DEV] Proposal for serious BC compatibility aka language versioning From: karoly@negyesi.net (Karoly Negyesi) Well, either I misunderstood the policy or it's broken. Here are some (note: please do not argue whether these are more correct than before, they very well might be but they broke backwards compatibility): For example, in 5.4 array_diff_assoc began to throw a notice when casting to string. Again in 5.4, using a string offset against a string throws a warning. It wasn't doing that before. If you want I can dig around in our issue queue for more backwards compatibility breaks but there are some. Regards, Karoly Negyesi On Sun, Feb 3, 2013 at 4:19 AM, Pierre Joye wrote: > hi, > > On Sun, Feb 3, 2013 at 12:36 PM, Karoly Negyesi wrote: >> Hi, >> >> So, if we are talking about PHP 6, then the opening > accompanied by the version it was written for, it was tested with and then >> the engine could switch to a compatibility mode for that version. >> >> Seems to me that this would solve the problem where a host can't upgrade to >> a more modern version for fear of breaking old code. Consequently, open >> source packages -- like Drupal I am deeply involved with -- can't use more >> modern PHP versions decreasing the "push" for hosts to upgrade. This is a >> devilish circle and it'd be great to break it. > > We have been there, no chance to go back again with such tags. > > Also the new release process RFC > (https://wiki.php.net/rfc/releaseprocess) solves the BC issues between > minor updates (5.4 to 5.5, or 5.3 to 5.4 f.e.). It is our and our > users role to explain that to their ISPs, admins, etc. > > Cheers, > -- > Pierre > > @pierrejoye