Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:31203 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17320 invoked by uid 1010); 23 Jul 2007 16:13:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 17304 invoked from network); 23 Jul 2007 16:13:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2007 16:13:19 -0000 Authentication-Results: pb1.pair.com smtp.mail=jeremy@peak8solutions.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=jeremy@peak8solutions.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain peak8solutions.com from 69.50.1.43 cause and error) X-PHP-List-Original-Sender: jeremy@peak8solutions.com X-Host-Fingerprint: 69.50.1.43 unknown Received: from [69.50.1.43] ([69.50.1.43:15431] helo=peak8solutions.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A7/93-27148-C93D4A64 for ; Mon, 23 Jul 2007 12:13:17 -0400 Content-class: urn:content-classes:message Date: Mon, 23 Jul 2007 10:13:05 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: In-Reply-To: <30bd80240707230902m5084b6d9te4489173675f22ec@mail.gmail.com> X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.5 X-MS-TNEF-Correlator: Thread-Topic: [PHP-DEV] Question about Namespace patch Thread-Index: AcfNQxlIRHA+7JedTDWVNjDLWdWeNAAACrBA References: <46A31D95.2080407@fischer.name> <46A4661A.6080202@zend.com> <200707231140.55535.pstradomski@gmail.com> <46A4BA4F.6090506@dealnews.com> <40CA6572-030F-43E2-8706-64D1167C527C@bitxtender.com> <30bd80240707230902m5084b6d9te4489173675f22ec@mail.gmail.com> To: =?iso-8859-1?Q?Nicolas_B=E9rard-Nault?= , "Derick Rethans" Cc: =?iso-8859-1?Q?David_Z=FClke?= , "PHP Internals" Subject: RE: [PHP-DEV] Question about Namespace patch From: jeremy@peak8solutions.com ("Jeremy Privett") Yes, because that's ABSOLUTELY the way to respond to the community that = has continued to support PHP. If that is what this discussion is going = to degrade to, you're essentially saying "Please, gives us feedback but = we're not listening." If this is the case, then I'll keep in mind and make sure it's known = that bringing your issues and feedback to the PHP Devs is such a lovely = waste of time and energy. Thanks. --- Jeremy Privett Software Developer Peak8 Solutions -----Original Message----- From: nicobn@gmail.com [mailto:nicobn@gmail.com] On Behalf Of Nicolas = B=E9rard-Nault Sent: Monday, July 23, 2007 10:03 AM To: Derick Rethans Cc: David Z=FClke; PHP Internals Subject: Re: [PHP-DEV] Question about Namespace patch Despite all the comments made on this list by countless people, it's = still Stanislav's way or the highway. I don't want to sound negative but come on... this is getting ridiculous. Stanislav, why don't you just tell everybody that you'll stop answering because the patch will stay AS IT = IS over your dead body anyway ? I think you'll save us all some time. This discussion is endless and not productive. I can't speak for anybody here but I think a vote by all people who have commit access to php-src would clarify this issue once and for all so we can just move along. But that's just my 2 cents. On 7/23/07, Derick Rethans wrote: > > On Mon, 23 Jul 2007, David Z=FClke wrote: > > > Am 23.07.2007 um 16:25 schrieb Brian Moon: > > > > > > import SQLAlchemy::Column > > > > import SQLAlchemy::Table > > > > import SQLAlchemy::Join > > > > import SQLAlchemy::ForeignKey > > > > import SQLAlchemy::Session > > > > import SQLAlchemy::Transaction > > > > > > Why use namespaces if you are going to do this? You are just = bringing > your > > > classes into the global name space. The nice thing about = namespaces > IMO, is > > > that I don't have to have a class named SQLAlchemy_Transaction. I = can > just > > > have a class named Transaction in the SQLAlchemy namespace. I can > then > > > create a new object using $obj =3D new SQLAlchemy::Transaction. > > > > Oh yes, sure, that must be the main point about namespaces - I can = use > "::" > > instead of "_" as a delimiter! Yay! > > You forgot that you can also move the "prefix" in front of the class > name to "namespace prefix!" > > > Come on, you can't be serious. > > I sort of agree, I don't see how the current implementation is really > useful for anything. > > regards, > Derick > -- > Derick Rethans > http://derickrethans.nl | http://ez.no | http://xdebug.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > --=20 Nicolas B=E9rard-Nault (nicobn@gmail.com) =C9tudiant D.E.C. Sciences, Lettres & Arts C=E9gep de Sherbrooke Homepage: http://nicobn.googlepages.com