Re: Re: cvs: php4 /pear Makefile.in /pear/CacheFunction_Cache.php

Quoting Sebastian Bergmann <sb@sebastian-bergmann.de>: > I was asked by a couple of people to commit this one to the PEAR CVS. It > would be non-sense to wrap it up in a class just because we want only > classes in PEAR. If it were an arbitrary decision that we only wanted classes in PEAR, then yes, it would be nonsense. Please read my email: I was resurrecting a discussion, and giving my opinion. I have no problem with the code being in PEAR. But there are valid reasons to consider whether or not we want to have function libraries inside of PEAR, and if we decide that we don't, then this should be converted sooner rather than later to minimize the impact on people who start using it. Also: while this is cool code and I think that the functionality _should_ be in PEAR as long as there isn't native PHP functionality to do the same, I think that we should keep in mind that PEAR is not the only way that php developers can share code. -chuck -- Charles Hagenbuch, <chuck@horde.org> "If you can't stand the heat, get out of the chicken!" - Baby Blues