Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15569 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29479 invoked by uid 1010); 24 Mar 2005 01:34:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 29464 invoked from network); 24 Mar 2005 01:34:16 -0000 Received: from unknown (HELO yahoo.co.kr) (127.0.0.1) by localhost with SMTP; 24 Mar 2005 01:34:16 -0000 X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:55085] helo=mail.zend.com) by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP id 3C/B2-50080-71912424 for ; Wed, 23 Mar 2005 20:34:16 -0500 Received: (qmail 28651 invoked from network); 24 Mar 2005 01:34:12 -0000 Received: from localhost (HELO ANDI-NOTEBOOK.zend.com) (127.0.0.1) by localhost with SMTP; 24 Mar 2005 01:34:12 -0000 Message-ID: <5.1.0.14.2.20050323173319.02eb3990@localhost> X-Sender: andi@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 23 Mar 2005 17:33:50 -0800 To: Lukas Smith ,internals@lists.php.net In-Reply-To: <20050321201142.37642.qmail@lists.php.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] extension naming From: andi@zend.com (Andi Gutmans) References: <20050321201142.37642.qmail@lists.php.net> Well it's a good question but I'm not sure how we'd call it. XML-RPC is already taken. Ideas? Andi At 09:11 PM 3/21/2005 +0100, Lukas Smith wrote: >Hi, > >I guess xmlprci is following the mysqli example. I am not sure if this is >a good idea to have new BC breaking versions of extensions append letters >like "i" (aka "improved") to solve the namespace issue. So I would like to >bring this topic up for discussion on this list before too many other >extensions blindly follow this example, just because of the lack of a >standarized alternative. > >Anyways I dont really know if anyone from php core cares about these kinds >of topics so just tell me to stfu before we get a needless flame. > >The obvious problem is: >What comes after "i"? >How transparent is this naming scheme to the user? > >We had to address a similar problem in PEAR and we currently have the >following regulation in place which is a solution which is not beautiful >either: >http://pear.php.net/group/docs/20031114-bbr.php > >I guess the only advantage to using letters to denote new major versions >is that I dont know anyone else using "i" as a postfix like this. So we >are less likely to clash with a theoretically possible xmlrpc2 standard if >we were to use the more common method of appending numbers. > >Also while xmlrpci is only a pecl ext for now is seems like it registers a >class called xmlrpc ("REGISTER_XMLRPCI_CLASS(xmlrpc, rpc, NULL, 0)"). I >dont think this is a good idea either. > >regards, >Lukas > >-- >PHP Internals - PHP Runtime Development Mailing List >To unsubscribe, visit: http://www.php.net/unsub.php