Re: no chance of multiple namespaces per file
| From: | Helgi Þormar Þorbjörnsson | Date: | Tue, 04 Dec 2007 20:23:55 +0000 |
| Subject: | Re: no chance of multiple namespaces per file | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-48670@lists.php.net to get a copy of this message | ||
You sure you didn't forget to email the mailing list too ? :)
Anyway either way enforce it everywhere or skip it all together, allowing
people to pick will be a MESSSSSSS IMHO :)
- Helgi
On Dec 4, 2007 8:20 PM, Tony Bibbs <tony@tonybibbs.com> wrote:
> I missed the entire put-it-all-in-one-file discussion but my take is that
> if supporting put-it-all-in-one-file is optional then using those packages
> choosing to support that should explicitly not support namespaces. Maybe
> this is something that can be enforced during packaging?
>
> --Tony
>
> ----- Original Message ----
> From: Helgi Þormar Þorbjörnsson <helgith@gmail.com>
> To: Gregory Beaver <greg@chiaraquartet.net>
> Cc: PEAR Announce <pear-dev@lists.php.net>
> Sent: Tuesday, December 4, 2007 1:49:27 PM
> Subject: Re: [PEAR-DEV] no chance of multiple namespaces per file
>
>
> On Dec 4, 2007 7:42 PM, Gregory Beaver <greg@chiaraquartet.net> 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?
>
>
> Isn't it quite useless to jump on the NS bandwagon if we can't support
> the
> whole put everything in a one big heap of a file approach ?
> Makes me wonder if we shouldn't just drop it.
>
> - Helgi
>
>
>
>