Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61398 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92176 invoked from network); 18 Jul 2012 14:27:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jul 2012 14:27:20 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajfweb@googlemail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajfweb@googlemail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.82.54 as permitted sender) X-PHP-List-Original-Sender: ajfweb@googlemail.com X-Host-Fingerprint: 74.125.82.54 mail-wg0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:42245] helo=mail-wg0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FF/D9-39169-7C7C6005 for ; Wed, 18 Jul 2012 10:27:20 -0400 Received: by wgx1 with SMTP id 1so1087946wgx.11 for ; Wed, 18 Jul 2012 07:27:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FBG0athw4gViLL7VGgq52cCeZ/6LFY/M8JNTb4oMFlE=; b=W+nNJL8yGR/tCeEC7T+Hcr23Sha0dIpPogtILub/cLfsAGOoF+wqAmYQB4wizcO/2L o03NI9AJecmI5TL8st/f9lRkAVo620Ol8e89nIrNpSQUbCcfzMEwqbiecOIwR7sTRf38 LLtZQqW2C/hH05HrpsTjGh62au856HYoSftnrlW8wOxOVj8Fir5Ro+wt4bcmNM2BjtOr eY+Kpv3W0ByVGeprRufjspbb12jWcnNxNnpSAAWvSFHkB9Tg/E4Ee0vAj9E5kVnma3Co HBjSdjqNrNMA+WCo9EQmQymFLmc60Wk5gaMNTJqNgPaCNTAvZ70JdmncL6NasfeMdzrb 7vUg== MIME-Version: 1.0 Received: by 10.180.106.97 with SMTP id gt1mr7091655wib.5.1342621636630; Wed, 18 Jul 2012 07:27:16 -0700 (PDT) Received: by 10.216.160.16 with HTTP; Wed, 18 Jul 2012 07:27:12 -0700 (PDT) Received: by 10.216.160.16 with HTTP; Wed, 18 Jul 2012 07:27:12 -0700 (PDT) In-Reply-To: References: Date: Wed, 18 Jul 2012 15:27:12 +0100 Message-ID: To: Kris Craig Cc: PHP internals list Content-Type: multipart/alternative; boundary=f46d04428066b816d004c51b7593 Subject: Re: [PHP-DEV] Docs: php.ini vs. parse_ini_file() From: ajfweb@googlemail.com (Andrew Faulds) --f46d04428066b816d004c51b7593 Content-Type: text/plain; charset=UTF-8 Sounds good, search engines aren't always super smart. On Jul 18, 2012 1:20 AM, "Kris Craig" 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. > > --Kris > --f46d04428066b816d004c51b7593--