Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24478
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:from:reply-to:organization:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id;
        b=pWQlbUL4+GUehXGZpleLmDjbYjKVxeHsR/qCsDckEs+Q102FMQ42JKR9ssPq0dwsmmHITD8+xkLJMa3kaKQCoNA16BJaNncDBCTGjMVSJvDH7tiF9tsQaVosMBi+tlNpalLlzRlKpwUr/G42sQl84JAVmB60RWvQC6kQCA8uis8=
Reply-To: boards@gmail.com
Organization: LX
To: internals@lists.php.net
Date: Tue, 18 Jul 2006 12:03:56 -0500
User-Agent: KMail/1.9.3
References: <EEB3CC8C-862D-4E2F-B98B-A0DF4E654632@prohost.org> <Pine.LNX.4.62.0607181437280.7330@localhost> <EE5AE40B-2610-47FB-93CB-27173E4C7D66@prohost.org>
In-Reply-To: <EE5AE40B-2610-47FB-93CB-27173E4C7D66@prohost.org>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart1741801.7TLWV81Hnz";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-ID: <200607181203.56676.boards@gmail.com>
Subject: Re: [PHP-DEV] Re: PHP 5.2 Status Update
From: boards@gmail.com (Matt Sicker)

--nextPart1741801.7TLWV81Hnz
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 18 July 2006 09:27, Ilia Alshanetsky wrote:
> The date extension functionality can be enabled, but we need to
> rename the date class to avoid naming conflicts encountered with PHP
> 5.1. There have been two names under consideration datetime and
> phpdate. Personally I'd prefer datetime, but after doing a quick
> search on google that seems like a popular name, already being used
> in various classes and libraries. phpdate (or PHPDate to comply with
> studly caps conventions ;-) ) on the otherhand is only used a very
> small number of times is minor classes therefor seems like a safe
> name.
>
> If you chose PHPDate is the class name, I would no objections to
> including the functionality, assuming there are no technical merits
> for not including the extension.
>
> On 18-Jul-06, at 8:39 AM, Derick Rethans wrote:
> > On Sat, 15 Jul 2006, Lukas Smith wrote:
> >> Ilia Alshanetsky wrote:
> >>> It's been quite sometime since 5.2 was branched and looking over
> >>> our "todo"
> >>> majority of planned changes were made. Therefor I'd like to make
> >>> an RC1 on
> >>> Thursday next week and start the stabilization cycle of 5.2, so
> >>> we can get a
> >>> final in about 2 months. Once we start stabilization cycle, no
> >>> new features
> >>> will be accepted, so please use this week to commit any missing
> >>> new features
> >>> or major patches that have been agreed upon and not yet applied.
> >
> > This caught be a bit by surprise as I was unavailabe the last two
> > weeks,
> > so I hope I am still in time with my todo items (enabling ext/date
> > finally, and adding ext/filter with a symlink).
> >
> > 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
>
> Ilia Alshanetsky
It'd be nice to have a php namespace, wouldn't it? ;)

Maybe you might not want to include that class until PHP6.  Or, how=20
about for backwards compatibility, you do prefix the class name with=20
PHP, but when namespaces come into play, using the php namespace=20
effectively removes the PHP prefix (e.g. PHPDate =3D=3D php::Date).
=2D-=20
Matt Sicker

--nextPart1741801.7TLWV81Hnz
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBEvRR85tcAKF5t41MRAvu6AJ9ZUZ5hCwlDHoKixkVBF6BDXST++wCggZgQ
/RYmX/FwJPxJP9i6osi7uVE=
=prqo
-----END PGP SIGNATURE-----

--nextPart1741801.7TLWV81Hnz--