Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28948
Return-Path: <mbneto@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 55402 invoked by uid 1010); 23 Apr 2007 00:35:01 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 55386 invoked from network); 23 Apr 2007 00:35:01 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 23 Apr 2007 00:35:01 -0000
Authentication-Results: pb1.pair.com header.from=mbneto@gmail.com; sender-id=pass; domainkeys=bad
Authentication-Results: pb1.pair.com smtp.mail=mbneto@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.178 as permitted sender)
DomainKey-Status: bad
X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01
X-PHP-List-Original-Sender: mbneto@gmail.com
X-Host-Fingerprint: 64.233.166.178 py-out-1112.google.com Linux 2.4/2.6
Received: from [64.233.166.178] ([64.233.166.178:17422] helo=py-out-1112.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id B1/A7-02716-23FFB264 for <internals@lists.php.net>; Sun, 22 Apr 2007 20:34:59 -0400
Received: by py-out-1112.google.com with SMTP id a25so1186899pyi
        for <internals@lists.php.net>; Sun, 22 Apr 2007 17:34:55 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
        b=p3pds9HZjDZgQOz57a0fmKx0IKeSOCKZx2KwKHAWunN42BOCbbI2nT3bB66Lvx+C17V50JEBCyhfakA2DgPu6UJBhvhNhQAEhRnYqoTVuCg03XlAp/KOjpy5D4zt7oAbUWz1z49hNu2YofBnkV1zpX7L76W4qW7eZ3sa8oOWPVk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=tGWU1KNS5/Z5hA40q2f8YVW770fR0MB7Y5V9jWiF1pQVYX/9jJu2+0nL9jzsirFwQ5tdYRbYgbe71K/c7g1CClnsjgZVAsJeLAEWJSECIzIj28iwbyL1vUwGAhc28rqmy+XtijZCK2PEEul7jX3UCjDp1XTIiXPmfLJYh2E2oFY=
Received: by 10.65.215.14 with SMTP id s14mr10648336qbq.1177288495753;
        Sun, 22 Apr 2007 17:34:55 -0700 (PDT)
Received: by 10.65.96.19 with HTTP; Sun, 22 Apr 2007 17:34:55 -0700 (PDT)
Message-ID: <5cf776b80704221734u30c0aa7ekc787804c82bc2a50@mail.gmail.com>
Date: Sun, 22 Apr 2007 20:34:55 -0400
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_45027_19596690.1177288495693"
Subject: Recommendations for PHP 6 'certified' code
From: mbneto@gmail.com (mbneto)

------=_Part_45027_19596690.1177288495693
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

I saw one post earlier at php-general asking for a list of recommendations /
practices that should be followed to guarantee that code will run fine when
PHP 6 comes out.

I've searched and could not find a 'definitive' list of features that will
change or be deprecated with PHP 6.  Having such a list would be great since
we could start to alert people so they can 'correct' existing code or  start
developing  in a  recommended manner to reduce further headaches...

------=_Part_45027_19596690.1177288495693--