Re: no chance of multiple namespaces per file

It may not matter. I see Derrick Rethans just sent a note to PHP-DEV suggesting it should be taken out completely. What a cluster kcuf this has become... --Tony ----- Original Message ---- From: Paul M Jones <pmjones@ciaweb.net> To: Joshua Eichorn <josh@bluga.net> Cc: Gregory Beaver <greg@chiaraquartet.net>; PEAR Announce <pear-dev@lists.php.net> Sent: Tuesday, December 4, 2007 4:14:35 PM Subject: Re: [PEAR-DEV] no chance of multiple namespaces per file On 04 Dec 2007, at 14:45, Joshua Eichorn wrote: > Gregory Beaver wrote: >> hi all, >> >> There's no chance of multiple namespaces per file. If that's an >> issue, >> we can drop namespaces (meaning forbid their usage) from the coding >> requirements in PEAR2. >> >> Comments? >> >> Greg >> >> > I don't have a problem with it. Once you have namespaces you can > use them to alias long names to short ones when coding. You don't > gain much by actually using the namespaces. We can also provide > example imports for shorter names. I have no problem with forbidding them either. With that in mind, I think we should be clear on a couple points: 1. *Do not* use formal PHP namespaces. 2. *Do* use informal namespaces (i.e. pseudo-namespace prefix on all class names, function names, global vars and global constants, et al). If there is some way to additionally say "if you must use formal PHP namespaces, do so in X fashion" that would be good, but I don't see offhand how it would be possible/reasonable to combine formal and informal namespaces. -- Paul M. Jones <http://paul-m-jones.com> Solar: Simple Object Library and Application Repository for PHP5. <http://solarphp.com> Join the Solar community wiki! <http://solarphp.org> Savant: The simple, elegant, and powerful solution for templates in PHP. <http://phpsavant.com> -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php