Re: Problem with Config package?

I understand where you are coming from. I'd "cvs remove" that file then and maybe rename the apache example to something that let's the first time user know it is, in fact, a file with sample code. I updated my code (which is in alpha itself) to use the new API. Thanks, slick package! --Tony On Fri, 15 Nov 2002, Bertrand Mansion wrote: > <tony@tonybibbs.com> wrote : > > > Please note the code snippets in README.Config uses the same bit of code I > > have (which I assume just needs updating). > > > > Also, the single example in the file iniCommented.php in the docs/ > > directory only shows the parse portion. It'd be nice to see a few other > > method calls in there (unless, of course, your intention is to add that to > > the README.Config). > > The README.Config has not been updated for v1. It still shows methods for > usage with pre 1 versions. On the other hand, the example in docs/ are for > v1 version. If you don't see enough methods in iniCommented.php, just look > at the apache example. The API is the same, whatever container you use. > > I won't touch the README.Config because it is not supposed to exist. Config > has been the only package in PEAR with such a file in a package root. IMO, > this file should have been put in a docs/ directory or directly in the > peardoc. > > Note also that you can use the older API if you prefer, but I don't know if > it is still being maintained. > > Good luck, > > Bertrand Mansion > Mamasam >