[PHP-DOC] cvs: phpdoc /en/reference/filter reference.xml
vrana Mon Mar 13 10:02:41 2006 UTC Modified files: /phpdoc/en/reference/filter reference.xml Log: experimental categorization, number_float flags http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/filter/reference.xml?r1=1.3r2=1.4diff_format=u Index: phpdoc/en/reference/filter/reference.xml diff -u phpdoc/en/reference/filter/reference.xml:1.3 phpdoc/en/reference/filter/reference.xml:1.4 --- phpdoc/en/reference/filter/reference.xml:1.3Sun Mar 12 09:19:09 2006 +++ phpdoc/en/reference/filter/reference.xmlMon Mar 13 10:02:41 2006 @@ -1,7 +1,8 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.3 $ -- +!-- $Revision: 1.4 $ -- !-- Purpose: basic.vartype -- !-- Membership: pecl -- +!-- State: experimental -- !-- Generated by xml_proto.php v2.4. Found in /scripts directory of phpdoc. -- reference id=ref.filter titleFilter Functions/title @@ -200,7 +201,11 @@ entryconstantFILTER_SANITIZE_NUMBER_FLOAT/constant/entry entrynumber_float/entry entry/entry -entry/entry +entry + constantFILTER_FLAG_ALLOW_FRACTION/constant, + constantFILTER_FLAG_ALLOW_THOUSAND/constant, + constantFILTER_FLAG_ALLOW_SCIENTIFIC/constant +/entry entry Remove all characters except digits, literal+-/literal and optionally literal.,eE/literal.
[PHP-DOC] cvs: phpdoc /en/reference/mime_magic reference.xml
vrana Mon Mar 13 10:23:29 2006 UTC Modified files: /phpdoc/en/reference/mime_magic reference.xml Log: Internal link to Fileinfo http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/mime_magic/reference.xml?r1=1.7r2=1.8diff_format=u Index: phpdoc/en/reference/mime_magic/reference.xml diff -u phpdoc/en/reference/mime_magic/reference.xml:1.7 phpdoc/en/reference/mime_magic/reference.xml:1.8 --- phpdoc/en/reference/mime_magic/reference.xml:1.7Sun Sep 4 19:39:19 2005 +++ phpdoc/en/reference/mime_magic/reference.xmlMon Mar 13 10:23:29 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.7 $ -- +!-- $Revision: 1.8 $ -- !-- Purpose: fileprocess.file -- !-- Membership: bundled -- !-- State: deprecated -- @@ -14,7 +14,7 @@ warning para This extension has been deprecated as the PECL extension - ulink url=url.pecl.package;fileinfofileinfo/ulink + link linkend=ref.fileinfoFileinfo/link provides the same functionality (and more) in a much cleaner way. /para /warning
[PHP-DOC] #36714 [NEW]: wrong squlite_query example
From: tobias dot nix at gmail dot com
Operating system: doesnt matter
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: wrong squlite_query example
Description:
The example1 is the following:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query('CREATE TABLE foo (bar varchar(10))');
sqlite_query(INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query('select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
On sqlite_query is a $db missing:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query($db, 'CREATE TABLE foo (bar varchar(10))');
sqlite_query($db, INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query($db,'select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
--
Edit bug report at http://bugs.php.net/?id=36714edit=1
--
Try a CVS snapshot (PHP 4.4):
http://bugs.php.net/fix.php?id=36714r=trysnapshot44
Try a CVS snapshot (PHP 5.1):
http://bugs.php.net/fix.php?id=36714r=trysnapshot51
Try a CVS snapshot (PHP 6.0):
http://bugs.php.net/fix.php?id=36714r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=36714r=fixedcvs
Fixed in release:
http://bugs.php.net/fix.php?id=36714r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=36714r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=36714r=needscript
Try newer version:http://bugs.php.net/fix.php?id=36714r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=36714r=support
Expected behavior:http://bugs.php.net/fix.php?id=36714r=notwrong
Not enough info:
http://bugs.php.net/fix.php?id=36714r=notenoughinfo
Submitted twice:
http://bugs.php.net/fix.php?id=36714r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=36714r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=36714r=php3
Daylight Savings: http://bugs.php.net/fix.php?id=36714r=dst
IIS Stability:http://bugs.php.net/fix.php?id=36714r=isapi
Install GNU Sed: http://bugs.php.net/fix.php?id=36714r=gnused
Floating point limitations: http://bugs.php.net/fix.php?id=36714r=float
No Zend Extensions: http://bugs.php.net/fix.php?id=36714r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=36714r=mysqlcfg
[PHP-DOC] cvs: phpdoc /en/reference/fileinfo reference.xml
vrana Mon Mar 13 10:29:51 2006 UTC Modified files: /phpdoc/en/reference/fileinfo reference.xml Log: External categorization http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/fileinfo/reference.xml?r1=1.2r2=1.3diff_format=u Index: phpdoc/en/reference/fileinfo/reference.xml diff -u phpdoc/en/reference/fileinfo/reference.xml:1.2 phpdoc/en/reference/fileinfo/reference.xml:1.3 --- phpdoc/en/reference/fileinfo/reference.xml:1.2 Thu Mar 9 14:19:20 2006 +++ phpdoc/en/reference/fileinfo/reference.xml Mon Mar 13 10:29:51 2006 @@ -1,7 +1,7 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- !-- Purpose: fileprocess.file -- -!-- Membership: pecl -- +!-- Membership: external, pecl -- !-- Generated by xml_proto.php v2.3. Found in /scripts directory of phpdoc. -- reference id=ref.fileinfo titleFileinfo Functions/title
[PHP-DOC] cvs: phpdoc /en/appendices extensions.xml
vrana Mon Mar 13 10:30:08 2006 UTC Modified files: /phpdoc/en/appendices extensions.xml Log: Update http://cvs.php.net/viewcvs.cgi/phpdoc/en/appendices/extensions.xml?r1=1.16r2=1.17diff_format=u Index: phpdoc/en/appendices/extensions.xml diff -u phpdoc/en/appendices/extensions.xml:1.16 phpdoc/en/appendices/extensions.xml:1.17 --- phpdoc/en/appendices/extensions.xml:1.16Mon Oct 3 11:25:07 2005 +++ phpdoc/en/appendices/extensions.xml Mon Mar 13 10:30:08 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=utf-8? -!-- $Revision: 1.16 $ -- +!-- $Revision: 1.17 $ -- !-- DO NOT TRANSLATE THIS FILE! All the content that is displayed on the extension categorization page in your translated manual @@ -23,6 +23,7 @@ listitemparaxref linkend=ref.classkit//para/listitem listitemparaxref linkend=ref.classobj//para/listitem listitemparaxref linkend=ref.ctype//para/listitem + listitemparaxref linkend=ref.filter//para/listitem listitemparaxref linkend=ref.funchand//para/listitem listitemparaxref linkend=ref.objaggregation//para/listitem listitemparaxref linkend=ref.var//para/listitem @@ -121,6 +122,7 @@ listitemparaxref linkend=ref.paradox//para/listitem listitemparaxref linkend=ref.pdo-dblib//para/listitem listitemparaxref linkend=ref.pdo-firebird//para/listitem + listitemparaxref linkend=ref.pdo-informix//para/listitem listitemparaxref linkend=ref.pdo-mysql//para/listitem listitemparaxref linkend=ref.pdo-oci//para/listitem listitemparaxref linkend=ref.pdo-odbc//para/listitem @@ -146,6 +148,7 @@ listitemparaxref linkend=ref.simplexml//para/listitem listitemparaxref linkend=ref.xml//para/listitem listitemparaxref linkend=ref.xmlreader//para/listitem +listitemparaxref linkend=ref.xmlwriter//para/listitem listitemparaxref linkend=ref.xsl//para/listitem listitemparaxref linkend=ref.xslt//para/listitem /itemizedlist @@ -183,6 +186,7 @@ listitemparaxref linkend=ref.bc//para/listitem listitemparaxref linkend=ref.gmp//para/listitem listitemparaxref linkend=ref.math//para/listitem + listitemparaxref linkend=ref.stats//para/listitem /itemizedlist /section @@ -191,6 +195,7 @@ itemizedlist listitemparaxref linkend=ref.crack//para/listitem + listitemparaxref linkend=ref.hash//para/listitem listitemparaxref linkend=ref.mcrypt//para/listitem listitemparaxref linkend=ref.mhash//para/listitem listitemparaxref linkend=ref.openssl//para/listitem @@ -208,6 +213,7 @@ listitemparaxref linkend=ref.mbstring//para/listitem listitemparaxref linkend=ref.pspell//para/listitem listitemparaxref linkend=ref.recode//para/listitem +listitemparaxref linkend=ref.unicode//para/listitem /itemizedlist /section @@ -222,6 +228,7 @@ listitemparaxref linkend=ref.dio//para/listitem listitemparaxref linkend=ref.dir//para/listitem listitemparaxref linkend=ref.fam//para/listitem + listitemparaxref linkend=ref.fileinfo//para/listitem listitemparaxref linkend=ref.filesystem//para/listitem listitemparaxref linkend=ref.mime-magic//para/listitem listitemparaxref linkend=ref.xattr//para/listitem @@ -325,9 +332,11 @@ itemizedlist listitemparaxref linkend=ref.cpdf//para/listitem listitemparaxref linkend=ref.fdf//para/listitem + listitemparaxref linkend=ref.gnupg//para/listitem listitemparaxref linkend=ref.ming//para/listitem listitemparaxref linkend=ref.pdf//para/listitem listitemparaxref linkend=ref.ps//para/listitem + listitemparaxref linkend=ref.rpmreader//para/listitem listitemparaxref linkend=ref.swf//para/listitem /itemizedlist /section @@ -369,6 +378,7 @@ listitemparaxref linkend=ref.dotnet//para/listitem listitemparaxref linkend=ref.printer//para/listitem listitemparaxref linkend=ref.w32api//para/listitem + listitemparaxref linkend=ref.win32ps//para/listitem listitemparaxref linkend=ref.win32service//para/listitem /itemizedlist /section @@ -413,6 +423,7 @@ listitemparaxref linkend=ref.stream//para/listitem listitemparaxref linkend=ref.strings//para/listitem listitemparaxref linkend=ref.tokenizer//para/listitem +listitemparaxref linkend=ref.unicode//para/listitem listitemparaxref linkend=ref.url//para/listitem listitemparaxref linkend=ref.var//para/listitem /itemizedlist @@ -440,6 +451,7 @@ listitemparaxref linkend=ref.ftp//para/listitem listitemparaxref linkend=ref.gettext//para/listitem listitemparaxref linkend=ref.gmp//para/listitem +listitemparaxref linkend=ref.hash//para/listitem listitemparaxref linkend=ref.hwapi//para/listitem listitemparaxref linkend=ref.ibase//para/listitem listitemparaxref linkend=ref.iconv//para/listitem @@ -512,10 +524,10 @@ listitemparaxref linkend=ref.dbx//para/listitem
[PHP-DOC] #36714 [Opn]: wrong squlite_query example
ID: 36714
Updated by: [EMAIL PROTECTED]
Reported By: tobias dot nix at gmail dot com
Status: Open
Bug Type: Documentation problem
Operating System: doesnt matter
PHP Version: Irrelevant
New Comment:
Can you provide a link to this example?
I can't seen to find it.
Previous Comments:
[2006-03-13 11:26:00] tobias dot nix at gmail dot com
Description:
The example1 is the following:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query('CREATE TABLE foo (bar varchar(10))');
sqlite_query(INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query('select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
On sqlite_query is a $db missing:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query($db, 'CREATE TABLE foo (bar varchar(10))');
sqlite_query($db, INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query($db,'select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
--
Edit this bug report at http://bugs.php.net/?id=36714edit=1
[PHP-DOC] #36714 [Opn-Csd]: wrong squlite_query example
ID: 36714
Updated by: [EMAIL PROTECTED]
Reported By: tobias dot nix at gmail dot com
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: doesnt matter
PHP Version: Irrelevant
New Comment:
Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at
http://www.php.net/downloads.php
Previous Comments:
[2006-03-13 11:31:49] [EMAIL PROTECTED]
Can you provide a link to this example?
I can't seen to find it.
[2006-03-13 11:26:00] tobias dot nix at gmail dot com
Description:
The example1 is the following:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query('CREATE TABLE foo (bar varchar(10))');
sqlite_query(INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query('select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
On sqlite_query is a $db missing:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query($db, 'CREATE TABLE foo (bar varchar(10))');
sqlite_query($db, INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query($db,'select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
--
Edit this bug report at http://bugs.php.net/?id=36714edit=1
[PHP-DOC] #36714 [Csd]: wrong squlite_query example
ID: 36714
User updated by: tobias dot nix at gmail dot com
Reported By: tobias dot nix at gmail dot com
Status: Closed
Bug Type: Documentation problem
Operating System: doesnt matter
PHP Version: Irrelevant
New Comment:
Sorry for missing link:
http://php.net/manual/de/function.sqlite-open.php
Previous Comments:
[2006-03-13 11:34:35] [EMAIL PROTECTED]
Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at
http://www.php.net/downloads.php
[2006-03-13 11:31:49] [EMAIL PROTECTED]
Can you provide a link to this example?
I can't seen to find it.
[2006-03-13 11:26:00] tobias dot nix at gmail dot com
Description:
The example1 is the following:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query('CREATE TABLE foo (bar varchar(10))');
sqlite_query(INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query('select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
On sqlite_query is a $db missing:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query($db, 'CREATE TABLE foo (bar varchar(10))');
sqlite_query($db, INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query($db,'select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
--
Edit this bug report at http://bugs.php.net/?id=36714edit=1
[PHP-DOC] cvs: phpdoc /en/reference/rpmreader/functions rpm-close.xml rpm-is-valid.xml
vrana Mon Mar 13 10:42:01 2006 UTC Modified files: /phpdoc/en/reference/rpmreader/functionsrpm-close.xml rpm-is-valid.xml Log: Fix return type http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/rpmreader/functions/rpm-close.xml?r1=1.1r2=1.2diff_format=u Index: phpdoc/en/reference/rpmreader/functions/rpm-close.xml diff -u phpdoc/en/reference/rpmreader/functions/rpm-close.xml:1.1 phpdoc/en/reference/rpmreader/functions/rpm-close.xml:1.2 --- phpdoc/en/reference/rpmreader/functions/rpm-close.xml:1.1 Sat Oct 15 14:17:20 2005 +++ phpdoc/en/reference/rpmreader/functions/rpm-close.xml Mon Mar 13 10:42:01 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.1 $ -- +!-- $Revision: 1.2 $ -- refentry id=function.rpm-close refnamediv refnamerpm_close/refname @@ -8,7 +8,7 @@ refsect1 role=description reftitle.description; methodsynopsis - typeboolean/typemethodnamerpm_close/methodname + typebool/typemethodnamerpm_close/methodname methodparamtyperesource/typeparameterrpmr/parameter/methodparam /methodsynopsis para http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/rpmreader/functions/rpm-is-valid.xml?r1=1.1r2=1.2diff_format=u Index: phpdoc/en/reference/rpmreader/functions/rpm-is-valid.xml diff -u phpdoc/en/reference/rpmreader/functions/rpm-is-valid.xml:1.1 phpdoc/en/reference/rpmreader/functions/rpm-is-valid.xml:1.2 --- phpdoc/en/reference/rpmreader/functions/rpm-is-valid.xml:1.1Sat Oct 15 14:17:20 2005 +++ phpdoc/en/reference/rpmreader/functions/rpm-is-valid.xmlMon Mar 13 10:42:01 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.1 $ -- +!-- $Revision: 1.2 $ -- refentry id=function.rpm-is-valid refnamediv refnamerpm_is_valid/refname @@ -8,7 +8,7 @@ refsect1 role=description reftitle.description; methodsynopsis - typeboolean/typemethodnamerpm_is_valid/methodname + typebool/typemethodnamerpm_is_valid/methodname methodparamtypestring/typeparameterfilename/parameter/methodparam /methodsynopsis para
[PHP-DOC] #36714 [Csd]: wrong squlite_query example
ID: 36714
Updated by: [EMAIL PROTECTED]
Reported By: tobias dot nix at gmail dot com
Status: Closed
Bug Type: Documentation problem
Operating System: doesnt matter
PHP Version: Irrelevant
New Comment:
German documentation is outdated. If you want to help with the
translation, contact [EMAIL PROTECTED]
Previous Comments:
[2006-03-13 11:41:51] tobias dot nix at gmail dot com
Sorry for missing link:
http://php.net/manual/de/function.sqlite-open.php
[2006-03-13 11:34:35] [EMAIL PROTECTED]
Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at
http://www.php.net/downloads.php
[2006-03-13 11:31:49] [EMAIL PROTECTED]
Can you provide a link to this example?
I can't seen to find it.
[2006-03-13 11:26:00] tobias dot nix at gmail dot com
Description:
The example1 is the following:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query('CREATE TABLE foo (bar varchar(10))');
sqlite_query(INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query('select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
On sqlite_query is a $db missing:
?php
if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
sqlite_query($db, 'CREATE TABLE foo (bar varchar(10))');
sqlite_query($db, INSERT INTO foo VALUES ('fnord'));
$result = sqlite_query($db,'select bar from foo');
var_dump(sqlite_fetch_array($result));
} else {
die ($sqliteerror);
}
?
--
Edit this bug report at http://bugs.php.net/?id=36714edit=1
[PHP-DOC] #36710 [Opn-Fbk]: self-contradictory documentation of escaping in single-quoted strings
ID: 36710 Updated by: [EMAIL PROTECTED] Reported By: swift at alum dot mit dot edu -Status: Open +Status: Feedback Bug Type: Documentation problem Operating System: Irrelevant PHP Version: Irrelevant New Comment: Why do you think a literal backslash needs to be escaped in only two cases: when it appears before a literal single quote and when it is the last character of the string is of course incorrect? It can be escaped on other places too but it NEEDS to be escaped only in these two cases. Current description is perfectly clear and right from my POV and doesn't need to be changed. Previous Comments: [2006-03-13 04:52:06] swift at alum dot mit dot edu Argh! This web interface told me I could edit my submission. That's not fully true, since I can't edit the main text, I can only add to it. So I've now posted two long discussions that differ only by a pair of commas, and I have no way to correct that. The second submission contains the corrected punctuation. [2006-03-13 04:48:51] swift at alum dot mit dot edu I quote from the node on strings in the PHP manual (www.php.net/manual/en/language.types.string.php) where it discusses single-quoted strings: I break into sentences which I reference below: (1) To specify a literal single quote, you will need to escape it with a backslash (\), like in many other languages. (2) If a backslash needs to occur before a single quote or at the end of the string, you need to double it. (3) Note that if you try to escape any other character, the backslash will also be printed! (4) So usually there is no need to escape the backslash itself. Sentence (1) is clear, though will should be omitted for better clarity. Sentence (2) means that a literal backslash needs to be escaped in only two cases: when it appears before a literal single quote and when it is the last character of the string. This is of course incorrect (it is contradicted by a correct example further down the page whose output is 'You deleted C:\*.*?'). What the author intends to say is much better expressed by the following: An escaped backslash (\\) likewise specifies a literal backslash, but it is not normally necessary to escape a literal backslash. Escaping a backslash is necessary only when the context would otherwise make the backslash into an escape operator -- that is, when it appears immediately before another backslash or the single quote terminating the string. Sentence (3) is unclear because it is unclear whether the reference of other is backslash or single quote or both. Also try to escape is a confusing hypothetical. A good revision would be: A backslash followed by any character besides a single quote or another backslash is a literal backslash. Sentence (4) is confusing because it's not clear that the backslash itself refers to a literal backslash or an escape-operator backslash. Omit this sentence: this section should deal only with how to specify a single quoted string. Discussion of applications of strings (such as regexps) which also use the backslash as an escape operator belongs somewhere else -- or at least should be clearly separate from the discussion of simply how to specify the contents of a string. Stringing together the suggested revisions above: To specify a literal single quote, you need to escape it with a backslash (\), like in many other languages. An escaped backslash (\\) likewise specifies a literal backslash, but it is not normally necessary to escape a literal backslash. Escaping a backslash is necessary only when the context would otherwise make the backslash into an escape operator -- that is, when it appears immediately before another backslash or the single quote terminating the string. A backslash followed by any character besides a single quote or another backslash is a literal backslash. [2006-03-13 04:43:22] swift at alum dot mit dot edu Description: I quote from the node on strings in the PHP manual (www.php.net/manual/en/language.types.string.php) where it discusses single-quoted strings: I break into sentences which I reference below: (1) To specify a literal single quote, you will need to escape it with a backslash (\), like in many other languages. (2) If a backslash needs to occur before a single quote or at the end of the string, you need to double it. (3) Note that if you try to escape any other character, the backslash will also be printed! (4) So usually there is no need to escape the backslash itself. Sentence (1) is clear, though will should be omitted for better clarity. Sentence (2) means that a literal backslash needs to be escaped in only two cases: when it appears before a literal single quote
[PHP-DOC] #36682 [Opn-Csd]: Heredoc not correctly parsed
ID: 36682 Updated by: [EMAIL PROTECTED] Reported By: daniele_dll at yahoo dot it -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Windows XP SP2 PHP Version: 5.1.2 New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Closing delimiter (possibly followed by a semicolon) must be followed by a newline too. Previous Comments: [2006-03-11 17:02:12] [EMAIL PROTECTED] Reclassifying as a doc problem. The behavior is correct. [2006-03-10 20:10:08] daniele_dll at yahoo dot it for [EMAIL PROTECTED]: in the description of the bug i've said that Terminating an heredoc without a newline cause a parse error ... if you try an heredoc into an eval, terminating the stuff without a new line after the heredoc's terminator, you get a parse error for evalued code! [code] echo eval(return EOF\r\nAll Works Correctly!\r\nEOF;); [/code] So there is this real problem (not related to other characters into the terminator line) Or the heredoc's manual page need to be updated with a new sentence, like [quote] Remember that after the heredoc terminator is necessary a new line. [/quote] Or this, possible, bug need to be corrected [2006-03-10 18:44:05] daniele_dll at yahoo dot it This doesn't make sense! Why an heredoc needs, to works correctly, a line only for it, without other stuff after the terminator (with a semicolon)? If there is a terminator and an ending semicolon, the command terminates there, so i should add other commands in the same line without problems. I don't think this is a really bug, but it is a logical bug. If the heredoc terminator is founded and there is a semicolon to terminate the line, a new command can be executed, like all other structures in php. i can write ?php $a = 1; $c = 'daniele_dll'; $b = 'test'; $a = $b; $b = $c; echo $a . $b . $c; echo print_r($_SERVER, true); die(ASD); ? without problems, so have heredoc that doesn't let to me to add multiple commands after the heredoc termination (plus semicolon) doesn't make sense for me. There is a particular reason to manage heredoc in this way? [2006-03-10 18:07:34] [EMAIL PROTECTED] Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php The terminating new line is obligatory [2006-03-10 17:50:07] daniele_dll at yahoo dot it Description: Terminating an heredoc without a newline cause a parse error. The reported code was tested with php 5.0.4, 5.0.5 and 5.1.2 Reproduce code: --- ?php echo HEREDOC_EOF Test Heredoc All works fine! HEREDOC_EOF;? Expected result: This code should output the text into the heredoc Actual result: -- The execution of this code return a parse error -- Edit this bug report at http://bugs.php.net/?id=36682edit=1
[PHP-DOC] cvs: phpdoc /en/language types.xml
vrana Mon Mar 13 11:01:37 2006 UTC Modified files: /phpdoc/en/language types.xml Log: heredoc must be followed by newline (bug #36682) http://cvs.php.net/viewcvs.cgi/phpdoc/en/language/types.xml?r1=1.161r2=1.162diff_format=u Index: phpdoc/en/language/types.xml diff -u phpdoc/en/language/types.xml:1.161 phpdoc/en/language/types.xml:1.162 --- phpdoc/en/language/types.xml:1.161 Thu Mar 9 06:39:45 2006 +++ phpdoc/en/language/types.xmlMon Mar 13 11:01:37 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.161 $ -- +!-- $Revision: 1.162 $ -- chapter id=language.types titleTypes/title @@ -820,7 +820,8 @@ It's also important to realize that the first character before the closing identifier must be a newline as defined by your operating system. This is literal\r/literal on Macintosh - for example. + for example. Closing delimiter (possibly followed by a semicolon) must + be followed by a newline too. /simpara simpara If this rule is broken and the closing identifier is not clean
[PHP-DOC] #36710 [Fbk]: self-contradictory documentation of escaping in single-quoted strings
ID: 36710 Updated by: [EMAIL PROTECTED] Reported By: swift at alum dot mit dot edu Status: Feedback Bug Type: Documentation problem Operating System: Irrelevant PHP Version: Irrelevant New Comment: I also think that the actual version is perfectly clear, and even clearer than the one you suggest. The four statements clearly state that : 1) In a single quoted string, there are 3 contexts where an escaping is *required* : a) to escape a single quote : 'Jymm\'s car' - Jymm's car b) to have a backslash at the end of a string : 'foo\\' - foo\ b) to have a \ printed before a single quote: 'foo\\\' bar' - foo\' bar 2) Out of these contexts, it is also _possible_ (not required) to escape a backslash. Otherwise, the backslash won't escape anything and thus will be printed. Previous Comments: [2006-03-13 11:54:50] [EMAIL PROTECTED] Why do you think a literal backslash needs to be escaped in only two cases: when it appears before a literal single quote and when it is the last character of the string is of course incorrect? It can be escaped on other places too but it NEEDS to be escaped only in these two cases. Current description is perfectly clear and right from my POV and doesn't need to be changed. [2006-03-13 04:52:06] swift at alum dot mit dot edu Argh! This web interface told me I could edit my submission. That's not fully true, since I can't edit the main text, I can only add to it. So I've now posted two long discussions that differ only by a pair of commas, and I have no way to correct that. The second submission contains the corrected punctuation. [2006-03-13 04:48:51] swift at alum dot mit dot edu I quote from the node on strings in the PHP manual (www.php.net/manual/en/language.types.string.php) where it discusses single-quoted strings: I break into sentences which I reference below: (1) To specify a literal single quote, you will need to escape it with a backslash (\), like in many other languages. (2) If a backslash needs to occur before a single quote or at the end of the string, you need to double it. (3) Note that if you try to escape any other character, the backslash will also be printed! (4) So usually there is no need to escape the backslash itself. Sentence (1) is clear, though will should be omitted for better clarity. Sentence (2) means that a literal backslash needs to be escaped in only two cases: when it appears before a literal single quote and when it is the last character of the string. This is of course incorrect (it is contradicted by a correct example further down the page whose output is 'You deleted C:\*.*?'). What the author intends to say is much better expressed by the following: An escaped backslash (\\) likewise specifies a literal backslash, but it is not normally necessary to escape a literal backslash. Escaping a backslash is necessary only when the context would otherwise make the backslash into an escape operator -- that is, when it appears immediately before another backslash or the single quote terminating the string. Sentence (3) is unclear because it is unclear whether the reference of other is backslash or single quote or both. Also try to escape is a confusing hypothetical. A good revision would be: A backslash followed by any character besides a single quote or another backslash is a literal backslash. Sentence (4) is confusing because it's not clear that the backslash itself refers to a literal backslash or an escape-operator backslash. Omit this sentence: this section should deal only with how to specify a single quoted string. Discussion of applications of strings (such as regexps) which also use the backslash as an escape operator belongs somewhere else -- or at least should be clearly separate from the discussion of simply how to specify the contents of a string. Stringing together the suggested revisions above: To specify a literal single quote, you need to escape it with a backslash (\), like in many other languages. An escaped backslash (\\) likewise specifies a literal backslash, but it is not normally necessary to escape a literal backslash. Escaping a backslash is necessary only when the context would otherwise make the backslash into an escape operator -- that is, when it appears immediately before another backslash or the single quote terminating the string. A backslash followed by any character besides a single quote or another backslash is a literal backslash. [2006-03-13 04:43:22] swift at alum dot mit dot edu Description: I quote from the node on strings in the PHP manual (www.php.net/manual/en/language.types.string.php) where
[PHP-DOC] #36728 [NEW]: Missing negative sign in documentation
From: heredy at sbcglobal dot net Operating system: XP PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: Missing negative sign in documentation Description: Regarding the documentation for explode(): This text is in the doc: --- If the limit parameter is negative, all components except the last limit are returned. This feature was added in PHP 5.1.0. --- I think there should be a negative sign (-) in front of the second instance if the word 'limit' in this sentence. --- If the limit parameter is negative, all components except the last -limit are returned. This feature was added in PHP 5.1.0. --- -- Edit bug report at http://bugs.php.net/?id=36728edit=1 -- Try a CVS snapshot (PHP 4.4): http://bugs.php.net/fix.php?id=36728r=trysnapshot44 Try a CVS snapshot (PHP 5.1): http://bugs.php.net/fix.php?id=36728r=trysnapshot51 Try a CVS snapshot (PHP 6.0): http://bugs.php.net/fix.php?id=36728r=trysnapshot60 Fixed in CVS: http://bugs.php.net/fix.php?id=36728r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=36728r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=36728r=needtrace Need Reproduce Script:http://bugs.php.net/fix.php?id=36728r=needscript Try newer version:http://bugs.php.net/fix.php?id=36728r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=36728r=support Expected behavior:http://bugs.php.net/fix.php?id=36728r=notwrong Not enough info: http://bugs.php.net/fix.php?id=36728r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=36728r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=36728r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=36728r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=36728r=dst IIS Stability:http://bugs.php.net/fix.php?id=36728r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=36728r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=36728r=float No Zend Extensions: http://bugs.php.net/fix.php?id=36728r=nozend MySQL Configuration Error:http://bugs.php.net/fix.php?id=36728r=mysqlcfg
[PHP-DOC] cvs: phpdoc /en/reference/strings/functions explode.xml
takagi Tue Mar 14 03:32:03 2006 UTC Modified files: /phpdoc/en/reference/strings/functions explode.xml Log: Missing negative sign (bug #36728) http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/strings/functions/explode.xml?r1=1.11r2=1.12diff_format=u Index: phpdoc/en/reference/strings/functions/explode.xml diff -u phpdoc/en/reference/strings/functions/explode.xml:1.11 phpdoc/en/reference/strings/functions/explode.xml:1.12 --- phpdoc/en/reference/strings/functions/explode.xml:1.11 Thu Apr 21 09:58:46 2005 +++ phpdoc/en/reference/strings/functions/explode.xml Tue Mar 14 03:32:02 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.11 $ -- +!-- $Revision: 1.12 $ -- !-- splitted from ./en/functions/strings.xml, last change in rev 1.2 -- refentry id=function.explode refnamediv @@ -32,7 +32,7 @@ /para para If the parameterlimit/parameter parameter is negative, all components - except the last parameterlimit/parameter are returned. This feature + except the last -parameterlimit/parameter are returned. This feature was added in PHP 5.1.0. /para para
[PHP-DOC] #36728 [Opn-Csd]: Missing negative sign in documentation
ID: 36728 Updated by: [EMAIL PROTECTED] Reported By: heredy at sbcglobal dot net -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: XP PHP Version: Irrelevant New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: [2006-03-13 23:27:19] heredy at sbcglobal dot net Description: Regarding the documentation for explode(): This text is in the doc: --- If the limit parameter is negative, all components except the last limit are returned. This feature was added in PHP 5.1.0. --- I think there should be a negative sign (-) in front of the second instance if the word 'limit' in this sentence. --- If the limit parameter is negative, all components except the last -limit are returned. This feature was added in PHP 5.1.0. --- -- Edit this bug report at http://bugs.php.net/?id=36728edit=1
