Re: Where to put C extension in pear?

> > A new directory pear/ext/foo directory hierachy perhaps? > > Should we use ext/ directory at all? My thinking was that a package is a > package, it uses the same naming rules and is no different from PEAR > classes. Besides, a package may contain both C and PHP files supporting > one another so I hope we can handle that situation. I suppose, although my xmms extension does not look like a PEAR class in any way. It is a simple procedural extension like most other normal PHP extensions and would serve as a basic building block that other more PEARish user-space classes could be built on top of. But I guess it could still live in pear/XMMS with a thin user-space PEAR wrapper that makes it look like a regular PEAR class. -Rasmus