Clever Geek Handbook

What is PEAR best suited for

I cannot wrap my head around PEAR or its customs. There is also some talk about its maintainability, so I think the best way to help me assess which subcomponents of my programs I might need is to ask what others have used it for. What did you use PEAR for and was it a good choice? and what did you decide to use for this, but in the end you settled on something else and why? I'm looking for specific examples, for example: "I had a bug page that sent mail and considered using PEAR :: Mail" or something like that.

Thanks everyone.

+2


source to share


3 answers


"PEAR" is not something in itself, it is a repository of many different extensions written by other people.

If you need basic authentication in your PHP application, go to http://pear.php.net/ and search for authentication . You now have a list of plugins that you can use to get the desired result.



There is a plugin for everything you might need. PEAR is neither good nor bad, every plugin inside the repository is good or bad, so it's up to you if the plugin works well for you.

+3


source


PEAR is not monolithic. This is not a frame or a single package. At its most basic level, PEAR is just a repository for modules, just like Perl CPAN (although it has become somewhat more coherent than CPAN for now).



Assess each extension on its merits to solve the problems you need to solve.

+3


source


PEAR is both a repository for packages and an infrastructure to install and maintain them, but it's worth noting that you can download and use packages from the browser (i.e. without using PEAR) and I think this is how most people refer to he.

+1


source






More articles:


All Articles