Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44000 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39474 invoked from network); 15 May 2009 22:18:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 May 2009 22:18:08 -0000 Authentication-Results: pb1.pair.com smtp.mail=sd@sven-drieling.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=sd@sven-drieling.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain sven-drieling.de from 212.6.122.13 cause and error) X-PHP-List-Original-Sender: sd@sven-drieling.de X-Host-Fingerprint: 212.6.122.13 mail1.ewetel.de Solaris 10 (beta) Received: from [212.6.122.13] ([212.6.122.13:64126] helo=mail1.ewetel.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/9B-27038-D1AED0A4 for ; Fri, 15 May 2009 18:18:07 -0400 Received: from [192.168.1.2] (host-091-097-106-020.ewe-ip-backbone.de [91.97.106.20]) by mail1.ewetel.de (8.12.1/8.12.9) with ESMTP id n4FMHtu1004101 for ; Sat, 16 May 2009 00:18:01 +0200 (CEST) To: internals@lists.php.net Date: Sat, 16 May 2009 00:14:30 +0200 User-Agent: KMail/1.9.10 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-ID: <200905160014.30691.sd@sven-drieling.de> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-CheckCompat: OK Subject: Re: [PHP-DEV] Re: Why does $_REQUEST exist? From: sd@sven-drieling.de (Sven Drieling) Am Freitag, 15. Mai 2009 schrieb Michael Shadle: Hallo, > There's gotta be a time in the natural evolution to "cut the cord" so > to speak - Python just launched 3.0 and dropped backwards > compatibility. Why can't PHP do the same in 6.0? :) (Or 5.3 for all I > care. But it really should align with a major revision #) Splitting PHP in 3 independent parts could help solving the backwards problem. - Library (Functions, Methods) - Virtual Machine (Zend Engine) - Compiler for PHP 5.2, PHP 6, ... Library | VM | P-Code/Bytecode / | \ / | \ 5.2 5.3 6.0 ... compiler So a system could contain a compiler for each major PHP version. Sourcecode written for PHP 5.2 will use PHP compiler 5.2, sourcecode for PHP 6.0 will use PHP compiler 6.0, ... No backwards problem for existing code. It's still necessary to update 5.2 code to use it with the PHP 6.0 compiler but the existing code does not prevent to use PHP 6.0 now for new scripts and classes. And this is IMO easier then using (fast) CGI or multiple instances of a webserver to have different versions of PHP on one server. There could also be different major versions of the library. tschuess [|8:) http://www.sven-drieling.de/