[dev] Names that conflicts with PEAR

[Blues]

On Sun, 18 Aug 2002, David U. wrote:
> >> Horde tries to provide Auth class. The same name is provided by PEAR,
> >> and if someone uses PEAR and Horde together it can make some
> >> confusions. This patch changes name from Auth* to Horde_Auth*
> > Can you provide a practical example where this becomes a problem?
> >> Now question - horde uses some parts of PEAR. Why does not use Auth
> >> (and other) class from there? If something is missing is that class
> >> should added there, not in horde's own classes.
> > Many reasons. One is that our Auth class was around well before PEAR
> > had one. Another is that I don't believe that PEAR should provide an
> > authentication class. But the people running PEAR these days disagree.
> You forgot to add that PEAR's Auth class offers like half a feature.  
> It's next to useless for most purposes.

well... work with them together to add missing ones :)

> Where are you seing namespace collisions 'Blues'?

For example - I've got scripts that give me what requires class and what
provides a file. This is very usefull - I know what pear package should I
install. When I tried to use it with horde, which uses PEAR, I was really
confused.

Remember - you provide class with different API and purpose.

I can send patches that solve rest of the conflicts, if you like to.

-- 
---------------------------------
pozdr.  Paweł Gołaszewski        
---------------------------------
CPU not found - software emulation...