Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61337
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nunninger.info from 87.106.55.207 cause and error)
Message-ID: <50052B5E.3030204@nunninger.info>
Date: Tue, 17 Jul 2012 11:07:42 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Nicholas Curtis <nich.curtis@gmail.com>
CC: internals@lists.php.net
References: <CAAyV7nFQc+4fWk2+aAJ_ctpqpsJGcYMR-fsgqDvPRzD36YJggg@mail.gmail.com> <5003DDF4.5080709@b1-systems.de> <CAJDSdj1rFEXoR4LAGLEL7Q1uEOr-E5wwi022uwaEV3QGTxaC_w@mail.gmail.com>
In-Reply-To: <CAJDSdj1rFEXoR4LAGLEL7Q1uEOr-E5wwi022uwaEV3QGTxaC_w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] 6.0 And Moving Forward
From: thomas@nunninger.info (Thomas Nunninger)

Hi,

On 07/17/2012 05:40 AM, Nicholas Curtis wrote:
 > Great Idea, would love to see current standard library in a legacy
 > namespace and a new standard library implemented as methods of
 > primitive types.

The idea to separate old and new behaviour has some charm.

 > $string = "Hello, World";
 > echo $strong->toUpper(); // HELLO, WORLD
 >
 > $int = 3;
 > echo $int->round(2); // 3.0
 >
 > While still preserving $legacy.strTopUpper($string) and 
$legacy.round($int)

I wouldn't do that because it implies two things:

- you have to change existing code (if I understand your syntax
   correctly)

- you could mix old and new style in one file


Somebody proposed (in some other thread some weeks ago) to introduce 
some code versioning. IIRC he proposed the "<?php6" opening tag instead 
of "<?php". (I'd prefer something like "<?php+" - but that's just a 
naming thing. And of course: You could still mix different styles in one 
file - but not in one php block. And that's easier to handle by coding 
conventions in the team.)

Versioning could be a chance to evolve the language and not to mess with 
existing code. BUT: I don't know if that's doable internally. And it's 
probably a lot of work...

Regards
Thomas