#45619 [Bgs]: parse_str() documentation

From: Date: Fri, 01 Aug 2008 18:43:04 +0000
Subject: #45619 [Bgs]: parse_str() documentation
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-1042@lists.php.net to get a copy of this message
ID: 45619 User updated by: the_N_Channel at hotmail dot com Reported By: the_N_Channel at hotmail dot com Status: Bogus Bug Type: Documentation problem Operating System: Windows PHP Version: Irrelevant New Comment: Cute. That answers the question but doesn't address the issue. Sure, now *I* know how to do it, but doesn't it seem relevant to add a Note after the two already existing notes that makes this explicit? Here's the code: <blockquote><p><b class="note">Note</b>: The default delimiter is set to &amp in the <em class="emphasis">php.ini.</em>, The current W3C standard also supports ;, if you'd like to change the delimiter, change the setting of <b> arg_separator.input </b> to suit your requirements. <br /> </p></blockquote> There, is that so hard? I'm pretty sure I'm not the only one who's had that question, who knows how many people are writing their own functions and wasting their time when it can be documented so simply? Previous Comments: ------------------------------------------------------------------------ [2008-08-01 11:24:53] dmytton@php.net The delimiter is set in php.ini. Default is &. Change arg_separator.input to suit your requirements. ------------------------------------------------------------------------ [2008-07-24 22:45:24] the_N_Channel at hotmail dot com Description: ------------ The documentation on parse_str() does not specify the delimiter used to parse the string. Given the examples authors quote in the comments section, it appears to be &. W3C also recommends ";", however in my trials I have not been able to make it work with ";". Is this delimiter assumed to be "&" in the function body, is there a magic place where this delimiter can be set? That kind of information seems like it should be in the doc for the function. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=45619&edit=1

« previous php.doc.bugs (#1042) next »