Re: Namespace Issues

Believe me, I will write the code for this in a flash if the wrangling over details can be worked out. Coding is the easy part :). I am dying to code the subpackages solution, and channels. Once this is complete, and SOME arrangement for handling BC is put into place, I can rest and stop bothering everyone about the PEAR core, as it will be ready for phpDocumentor 2.0. Regards, Greg Alan Knowles wrote:

I think the archives show the general gist of this: pear install Calander //.. - would check pear first, then other channels you have registered.. pear install PECL:Calander // - only pecl... pear install PEAR:Calander // - specifically PEAR pear install Horde:Calander // - specifically Horde Exact syntax hasnt been agreed on, but afaik there arent any major issues with this, other than someone bothering to write the code.. :) Regards Alan Greg Beaver wrote:

Hi, The channel solution wouldn't solve the issue, unless every class in a channel was prefixed like PEAR_Calendar PECL_Calendar (something I would be in favor of, but I'm sure nobody else in PEAR would be, judging by the response to BC efforts) Regards, Greg Lukas Smith wrote:

From: l0t3k [mailto:cshmoove@bellsouth.net] Sent: Wednesday, October 29, 2003 1:21 PM

What do we do, if anything at all, with possible PEAR/PECL namespace clashes ? in particular i've been working on an extension which i hope at some point to replace a bit of the work in I18N branch (not the problem). One of the exported classes is Calendar, which converts between a date/time value and a set of integer fields such as YEAR, MONTH, DAY, HOUR (i also have JapaneseCalendar and BuddhistCalendar). This of course clashes with the Calendar class that Harry Feucks recently committed. Comments ?

We are planning on adding "channel" support. PEAR and PECL would then be separate channels. Regards, Lukas