Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61412
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKOpQSxOE593FUFHh4Hj2PpX0-mrt8Si=ZwY9k4rOyC+0GXWEw@mail.gmail.com>
References: <CAKOpQSxOE593FUFHh4Hj2PpX0-mrt8Si=ZwY9k4rOyC+0GXWEw@mail.gmail.com>
Date: Wed, 18 Jul 2012 17:45:02 +0100
Message-ID: <CADNQb0VrYadLmL+yNBypAgY3do+srxp1ion=JSc4TPjL0Q18Ow@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Docs: php.ini vs. parse_ini_file()
From: hannes.magnusson@gmail.com (Hannes Magnusson)

On Wed, Jul 18, 2012 at 1:19 AM, Kris Craig <kris.craig@gmail.com> wrote:
> I just noticed something that I hadn't really thought about before.  I
> couldn't remember the name of the function for parsing INI files so I did a
> quick search.  It took me straight to the page for php.ini directives.  I
> had to select "online documentation" from the dropdown and try again, this
> time navigating down to the third result.
>
> Not overly cumbersome, of course, but I started thinking that maybe this
> could be more difficult for someone who might be newer to PHP.  I also
> tried a Google search for 'php ini' (no quotes) to see what I'd get, and
> the first 15 results (all of the first page and the top half of the second)
> were for php.ini stuff.  The 16th result was finally the parse_ini_file()
> function.  A lot of newbies in particular use Google as their first stop
> when trying to find PHP functions for doing stuff, so this could give some
> people the impression that PHP doesn't even have an INI parsing function.
>
>
> Of course, most of this we really have no control over, but I would like to
> propose adding a link to parse_ini_file() on the php.ini man pages (perhaps
> something along the lines of, "Are you looking for....?").  I can make the
> edits myself but I'd like to see what y'all think first.
>


I don't understand why on earth your are mailing the PHP *internal
developer mailinglist* with this matter?

If you have any improvement suggestions for the documentations:
https://edit.php.net

-Hannes