[PHP-DOC] cvs: phpdoc /en/reference/classobj/functions is-a.xml
seanTue Feb 24 00:54:36 2004 EDT Modified files: /phpdoc/en/reference/classobj/functions is-a.xml Log: added example http://cvs.php.net/diff.php/phpdoc/en/reference/classobj/functions/is-a.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/reference/classobj/functions/is-a.xml diff -u phpdoc/en/reference/classobj/functions/is-a.xml:1.3 phpdoc/en/reference/classobj/functions/is-a.xml:1.4 --- phpdoc/en/reference/classobj/functions/is-a.xml:1.3 Thu May 30 10:02:40 2002 +++ phpdoc/en/reference/classobj/functions/is-a.xml Tue Feb 24 00:54:36 2004 @@ -1,5 +1,5 @@ - + @@ -20,6 +20,30 @@ This function returns &true; if the object is of this class or has this class as one of its parents, &false; otherwise. + + +An exec example + + + + + See also get_class, get_parent_class, and
[PHP-DOC] cvs: phpdoc /en/reference/strings/functions strip-tags.xml
seanTue Feb 24 00:46:40 2004 EDT Modified files: /phpdoc/en/reference/strings/functions strip-tags.xml Log: swapped for (same for closing tags) http://cvs.php.net/diff.php/phpdoc/en/reference/strings/functions/strip-tags.xml?r1=1.7&r2=1.8&ty=u Index: phpdoc/en/reference/strings/functions/strip-tags.xml diff -u phpdoc/en/reference/strings/functions/strip-tags.xml:1.7 phpdoc/en/reference/strings/functions/strip-tags.xml:1.8 --- phpdoc/en/reference/strings/functions/strip-tags.xml:1.7Mon Feb 23 18:43:07 2004 +++ phpdoc/en/reference/strings/functions/strip-tags.xmlTue Feb 24 00:46:40 2004 @@ -1,5 +1,5 @@ - + @@ -28,13 +28,13 @@ and PHP 4.0b3. Since PHP 4.3.0, HTML comments are also stripped. - + Because strip_tags does not actually validate the HTML, partial, or broken tags can result in the removal of more text/data than expected. - +
[PHP-DOC] cvs: phpdoc /en/reference/exec/functions exec.xml
seanMon Feb 23 21:22:26 2004 EDT Modified files: /phpdoc/en/reference/exec/functions exec.xml Log: Added a simple example (could use more, but at least it has one now) http://cvs.php.net/diff.php/phpdoc/en/reference/exec/functions/exec.xml?r1=1.10&r2=1.11&ty=u Index: phpdoc/en/reference/exec/functions/exec.xml diff -u phpdoc/en/reference/exec/functions/exec.xml:1.10 phpdoc/en/reference/exec/functions/exec.xml:1.11 --- phpdoc/en/reference/exec/functions/exec.xml:1.10Tue Feb 17 21:51:09 2004 +++ phpdoc/en/reference/exec/functions/exec.xml Mon Feb 23 21:22:26 2004 @@ -1,5 +1,5 @@ - + @@ -39,6 +39,20 @@ return status of the executed command will be written to this variable. + + + An exec example + + + + + &warn.escapeshell; ¬e.exec-bg; ¬e.exec-path;
[PHP-DOC] #27361 [Opn]: strip_tags() doesn't fail on incomplete tag if there is non-html output before.
ID: 27361 Updated by: [EMAIL PROTECTED] Reported By: stu-php at better dot domain dot name Status: Open -Bug Type: Strings related +Bug Type: Documentation problem Operating System: Windows Server 2003 PHP Version: 5.0.0b4 (beta4) New Comment: The fact that strip_tags() does not validate HTML and can strip excess data when encountering incomplete tags should be documented. Previous Comments: [2004-02-23 16:57:12] stu-php at better dot domain dot name In one line, ok. strip_tags() doesn't error in the way it says it should on the function documentation page. That should be clear and concise enough. Take a look at http://better.domain.name/php/ and tell me if the files there represent expected outcomes of strip_tags() usage. [2004-02-23 16:55:25] stu-php at better dot domain dot name The function returns an error if there is text in one place, but NOT if there is text in another set of places, or nowhere at all. How is that NOT a bug? If I were relying on this function to give me accurate error information in an if statement or something then I wouldn't want it erroring if and when it felt like it. If it's supposed to strip html and error on invalid tags and then it goes ahead and fails to error because there is no text before the broken tag then there's a problem. Consider: http://better.domain.name/php/strips.phps The output has to be seen by viewing the source of http://better.domain.name/php/strips.php as it's completely erroneous output at the moment. Is that the expected behaviour? [2004-02-23 16:39:53] [EMAIL PROTECTED] Explain in one line what the bug is then...I don't see it either. [2004-02-23 16:36:36] stu-php at better dot domain dot name This is NOT a bogus bug. Just because the MAIN functionality of the function is there does not mean that there is not a bug here. The function behaves in an unexpected manner. That is a bug. If the documentation contradicts the actual function then something needs to be fixed. Either the documentation or the function code. [2004-02-23 13:54:24] [EMAIL PROTECTED] Try outputting the actual result of the strip_tags() and you'll see that it works perfectly. (strip_tags() is not any validator...whatever the docs say) The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/27361 -- Edit this bug report at http://bugs.php.net/?id=27361&edit=1
[PHP-DOC] cvs: phpdoc /en/reference/mbstring reference.xml
derek Mon Feb 23 18:12:00 2004 EDT Modified files: /phpdoc/en/reference/mbstring reference.xml Log: Grammatical Fix http://cvs.php.net/diff.php/phpdoc/en/reference/mbstring/reference.xml?r1=1.15&r2=1.16&ty=u Index: phpdoc/en/reference/mbstring/reference.xml diff -u phpdoc/en/reference/mbstring/reference.xml:1.15 phpdoc/en/reference/mbstring/reference.xml:1.16 --- phpdoc/en/reference/mbstring/reference.xml:1.15 Sun Dec 21 09:42:20 2003 +++ phpdoc/en/reference/mbstring/reference.xml Mon Feb 23 18:12:00 2004 @@ -1,5 +1,5 @@ - + Multi-Byte String Functions Multi-Byte String @@ -314,9 +314,9 @@ Because almost PHP application written for language using single-byte character encoding, there are some difficulties for - multibyte string handling including Japanese. Almost PHP string + multibyte string handling including Japanese. Most PHP string functions such as substr do not support - multibyte string. + multibyte strings. Multibyte extension (mbstring) has some PHP string functions
[PHP-DOC] cvs: phpdoc /en/reference/strings/functions strip-tags.xml
seanMon Feb 23 18:43:07 2004 EDT Modified files: /phpdoc/en/reference/strings/functions strip-tags.xml Log: don't mind me, just fixing my own ugly text http://cvs.php.net/diff.php/phpdoc/en/reference/strings/functions/strip-tags.xml?r1=1.6&r2=1.7&ty=u Index: phpdoc/en/reference/strings/functions/strip-tags.xml diff -u phpdoc/en/reference/strings/functions/strip-tags.xml:1.6 phpdoc/en/reference/strings/functions/strip-tags.xml:1.7 --- phpdoc/en/reference/strings/functions/strip-tags.xml:1.6Mon Feb 23 18:30:30 2004 +++ phpdoc/en/reference/strings/functions/strip-tags.xmlMon Feb 23 18:43:07 2004 @@ -1,5 +1,5 @@ - + @@ -31,7 +31,8 @@ Because strip_tags does not actually validate the - HTML, partial, or broken tags can result in unwanted results. + HTML, partial, or broken tags can result in the removal of more + text/data than expected.
[PHP-DOC] #27361 [Opn->Csd]: strip_tags() doesn't fail on incomplete tag if there is non-html output before.
ID: 27361 Updated by: [EMAIL PROTECTED] Reported By: stu-php at better dot domain dot name -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Windows Server 2003 PHP Version: 5.0.0b4 (beta4) -Assigned To: +Assigned To: sean 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. removed "It errors on the side of caution in case of incomplete or bogus tags." and added a warning: Because strip_tags does not actually validate the HTML, partial, or broken tags can result in unwanted results. Previous Comments: [2004-02-23 18:06:13] [EMAIL PROTECTED] The fact that strip_tags() does not validate HTML and can strip excess data when encountering incomplete tags should be documented. [2004-02-23 16:57:12] stu-php at better dot domain dot name In one line, ok. strip_tags() doesn't error in the way it says it should on the function documentation page. That should be clear and concise enough. Take a look at http://better.domain.name/php/ and tell me if the files there represent expected outcomes of strip_tags() usage. [2004-02-23 16:55:25] stu-php at better dot domain dot name The function returns an error if there is text in one place, but NOT if there is text in another set of places, or nowhere at all. How is that NOT a bug? If I were relying on this function to give me accurate error information in an if statement or something then I wouldn't want it erroring if and when it felt like it. If it's supposed to strip html and error on invalid tags and then it goes ahead and fails to error because there is no text before the broken tag then there's a problem. Consider: http://better.domain.name/php/strips.phps The output has to be seen by viewing the source of http://better.domain.name/php/strips.php as it's completely erroneous output at the moment. Is that the expected behaviour? [2004-02-23 16:39:53] [EMAIL PROTECTED] Explain in one line what the bug is then...I don't see it either. [2004-02-23 16:36:36] stu-php at better dot domain dot name This is NOT a bogus bug. Just because the MAIN functionality of the function is there does not mean that there is not a bug here. The function behaves in an unexpected manner. That is a bug. If the documentation contradicts the actual function then something needs to be fixed. Either the documentation or the function code. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/27361 -- Edit this bug report at http://bugs.php.net/?id=27361&edit=1
[PHP-DOC] cvs: phpdoc /en/reference/strings/functions strip-tags.xml
seanMon Feb 23 18:30:31 2004 EDT Modified files: /phpdoc/en/reference/strings/functions strip-tags.xml Log: Added a warning, see bug #27361 http://cvs.php.net/diff.php/phpdoc/en/reference/strings/functions/strip-tags.xml?r1=1.5&r2=1.6&ty=u Index: phpdoc/en/reference/strings/functions/strip-tags.xml diff -u phpdoc/en/reference/strings/functions/strip-tags.xml:1.5 phpdoc/en/reference/strings/functions/strip-tags.xml:1.6 --- phpdoc/en/reference/strings/functions/strip-tags.xml:1.5Tue Jan 27 11:01:45 2004 +++ phpdoc/en/reference/strings/functions/strip-tags.xmlMon Feb 23 18:30:30 2004 @@ -1,5 +1,5 @@ - + @@ -15,8 +15,7 @@ This function tries to return a string with all HTML and PHP tags - stripped from a given str. It errors on - the side of caution in case of incomplete or bogus tags. It uses + stripped from a given str. It uses the same tag stripping state machine as the fgetss function. @@ -29,6 +28,12 @@ and PHP 4.0b3. Since PHP 4.3.0, HTML comments are also stripped. + + + Because strip_tags does not actually validate the + HTML, partial, or broken tags can result in unwanted results. + +
[PHP-DOC] #27369 [Bgs->Opn]: RFE change in function.mysql-fetch-array.html
ID: 27369 User updated by: nospam at webdragon dot net Reported By: nospam at webdragon dot net -Status: Bogus +Status: Open Bug Type: Documentation problem Operating System: Linux (Fedora Core 1) PHP Version: Irrelevant New Comment: on the contrary, what's changed is _clarity_ it's either this, or TWO SQL queries, thus: 1. Query with duplicate field names SELECT t1.field, t2.field FROM t1, t2 2. Query with aliased duplicate field names SELECT t1.field AS foo, t2.field AS bar FROM t1, t2 since the Query presented in the existing docs is quite obviously one that does _not_ have duplicate field names in the result, since they are _already aliased in the example presented_, therefore the requested change. It presents the information in a slightly clearer manner with a minimum of additional bytes of info and is less confusing. Lest you forget, this documentation is not for people who already KNOW what you're talking about intimately. It's for people who haven't got a clue (or haven't had their coffee yet). The more clearly you can present your instructions, the fewer stupid questions and confused users you'll have. QED Previous Comments: [2004-02-23 15:05:19] [EMAIL PROTECTED] I don't see any interess in this patch, as nothing is changed. [2004-02-23 13:07:55] nospam at webdragon dot net Description: Following is a patch to the documentation to make the aliasing issue slightly clearer. I (in my caffeine deprived state) not only failed to realize that you were referring to aliasing via mysql, but didn't notice that the query below was doing that very thing in mysql. This patch makes this slightly clearer. (hopefully linewrapping won't bollix this) Reproduce code: --- --- function.mysql-fetch-array.html 2004-02-08 16:43:54.0 -0500 +++ function.mysql-fetch-array.new.html 2004-02-23 13:08:26.0 -0500 @@ -144,7 +144,7 @@ >Example 1. Query with duplicate field namesExample 1. Query with aliased duplicate field namesselect table1.field as foo, table2.field as bar from table1, table2SELECT table1.field AS foo, table2.field AS bar FROM table1, table2 \ No newline at end of file +> -- Edit this bug report at http://bugs.php.net/?id=27369&edit=1
Re: [PHP-DOC] LiveDocs TOC problem
The command line scripts are designed to run with PHP-CLI, which implies the -q option. Goba Patric Stout wrote: Hi all, I was just trying to compile LiveDocs, and I run into one big problem. I don't know if it is a config problem on my side, so I don't want to commit it. That's why this post. My system: Windows, Cygwin. My problem: the TOC doesn't work. The problem is that the file toc-insert.sql starts with: Content-type: text/html X-Powered-By: PHP/4.3.4 The solution to this is to run php.exe with -q. When I add this (line 39 of build.sh), it works perfect. Just my 2 cents. Patric Stout
[PHP-DOC] LiveDocs TOC problem
Hi all, I was just trying to compile LiveDocs, and I run into one big problem. I don't know if it is a config problem on my side, so I don't want to commit it. That's why this post. My system: Windows, Cygwin. My problem: the TOC doesn't work. The problem is that the file toc-insert.sql starts with: Content-type: text/html X-Powered-By: PHP/4.3.4 The solution to this is to run php.exe with -q. When I add this (line 39 of build.sh), it works perfect. Just my 2 cents. Patric Stout
[PHP-DOC] #27369 [Opn->Bgs]: RFE change in function.mysql-fetch-array.html
ID: 27369 Updated by: [EMAIL PROTECTED] Reported By: nospam at webdragon dot net -Status: Open +Status: Bogus Bug Type: Documentation problem Operating System: Linux (Fedora Core 1) PHP Version: Irrelevant New Comment: I don't see any interess in this patch, as nothing is changed. Previous Comments: [2004-02-23 13:07:55] nospam at webdragon dot net Description: Following is a patch to the documentation to make the aliasing issue slightly clearer. I (in my caffeine deprived state) not only failed to realize that you were referring to aliasing via mysql, but didn't notice that the query below was doing that very thing in mysql. This patch makes this slightly clearer. (hopefully linewrapping won't bollix this) Reproduce code: --- --- function.mysql-fetch-array.html 2004-02-08 16:43:54.0 -0500 +++ function.mysql-fetch-array.new.html 2004-02-23 13:08:26.0 -0500 @@ -144,7 +144,7 @@ >Example 1. Query with duplicate field namesExample 1. Query with aliased duplicate field namesselect table1.field as foo, table2.field as bar from table1, table2SELECT table1.field AS foo, table2.field AS bar FROM table1, table2 \ No newline at end of file +> -- Edit this bug report at http://bugs.php.net/?id=27369&edit=1
[PHP-DOC] #27369 [NEW]: RFE change in function.mysql-fetch-array.html
From: nospam at webdragon dot net Operating system: Linux (Fedora Core 1) PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: RFE change in function.mysql-fetch-array.html Description: Following is a patch to the documentation to make the aliasing issue slightly clearer. I (in my caffeine deprived state) not only failed to realize that you were referring to aliasing via mysql, but didn't notice that the query below was doing that very thing in mysql. This patch makes this slightly clearer. (hopefully linewrapping won't bollix this) Reproduce code: --- --- function.mysql-fetch-array.html 2004-02-08 16:43:54.0 -0500 +++ function.mysql-fetch-array.new.html 2004-02-23 13:08:26.0 -0500 @@ -144,7 +144,7 @@ >Example 1. Query with duplicate field namesExample 1. Query with aliased duplicate field namesselect table1.field as foo, table2.field as bar from table1, table2SELECT table1.field AS foo, table2.field AS bar FROM table1, table2 \ No newline at end of file +> -- Edit bug report at http://bugs.php.net/?id=27369&edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=27369&r=trysnapshot4 Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=27369&r=trysnapshot5 Fixed in CVS: http://bugs.php.net/fix.php?id=27369&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=27369&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=27369&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=27369&r=needscript Try newer version: http://bugs.php.net/fix.php?id=27369&r=oldversion Not developer issue:http://bugs.php.net/fix.php?id=27369&r=support Expected behavior: http://bugs.php.net/fix.php?id=27369&r=notwrong Not enough info:http://bugs.php.net/fix.php?id=27369&r=notenoughinfo Submitted twice:http://bugs.php.net/fix.php?id=27369&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=27369&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=27369&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=27369&r=dst IIS Stability: http://bugs.php.net/fix.php?id=27369&r=isapi Install GNU Sed:http://bugs.php.net/fix.php?id=27369&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=27369&r=float
Re: [PHP-DOC] Re: [PHP-DEV] Migration Appendice
Hi There is a typo in the proto for array_diff_uassoc() The 'u' is missing in the function name. Regards Conni
[PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Migration Appendice
Hello Gabor, Monday, February 23, 2004, 7:49:01 PM, you wrote: >> Paragraph: Classes must be declared before used >> is no longer true. For most cases this is allowed now. > What are those cases when this will be a problem? Having "most cases" in > the documentation without an explanation would be bad practice IMHO... IIRC then only standard classes without interfaces work. -- Best regards, Marcusmailto:[EMAIL PROTECTED]
[PHP-DOC] Re: [PHP-DEV] Migration Appendice
Hello Marcus, Monday, February 23, 2004, 6:42:06 PM, you wrote: > Hello Nuno, > Paragraph: Classes must be declared before used > is no longer true. For most cases this is allowed now. > Other notes: ext/domxml is replaced by ext/dom which is w3c dom > compliant. ext/tidy was added to the default distribution and its > method names were changed to studlyCaps convention. > ext/sqlite now supports an oo interface and throws exception instead > of errors when that is used. Further more ext/mysql does no longer include the lib I saw you also mention what is new: ext/mysqli, ext/spl and ext/simplexml were added. > regards > marcus > Monday, February 23, 2004, 6:22:57 PM, you wrote: >> Hi, >> Today I've finished writing the 'Migrating from PHP 4 to PHP 5' appendice. >> I would like you to review it to check if something is missing or incorrect. >> As the on-line version is outdated, use livedocs at: >> http://docs.php.net/en/migration5.html >> thanks, >> Nuno > -- > Best regards, > Marcusmailto:[EMAIL PROTECTED] -- Best regards, Marcusmailto:[EMAIL PROTECTED]
Re: [PHP-DOC] Re: [PHP-DEV] Migration Appendice
Paragraph: Classes must be declared before used is no longer true. For most cases this is allowed now. What are those cases when this will be a problem? Having "most cases" in the documentation without an explanation would be bad practice IMHO... Goba
[PHP-DOC] Re: [PHP-DEV] Migration Appendice
Hello Nuno, Paragraph: Classes must be declared before used is no longer true. For most cases this is allowed now. Other notes: ext/domxml is replaced by ext/dom which is w3c dom compliant. ext/tidy was added to the default distribution and its method names were changed to studlyCaps convention. ext/sqlite now supports an oo interface and throws exception instead of errors when that is used. regards marcus Monday, February 23, 2004, 6:22:57 PM, you wrote: > Hi, > Today I've finished writing the 'Migrating from PHP 4 to PHP 5' appendice. > I would like you to review it to check if something is missing or incorrect. > As the on-line version is outdated, use livedocs at: > http://docs.php.net/en/migration5.html > thanks, > Nuno -- Best regards, Marcusmailto:[EMAIL PROTECTED]
[PHP-DOC] cvs: phpdoc /entities global.ent
georg Mon Feb 23 12:37:07 2004 EDT Modified files: /phpdoc/entitiesglobal.ent Log: added url for MySQL world sample database http://cvs.php.net/diff.php/phpdoc/entities/global.ent?r1=1.168&r2=1.169&ty=u Index: phpdoc/entities/global.ent diff -u phpdoc/entities/global.ent:1.168 phpdoc/entities/global.ent:1.169 --- phpdoc/entities/global.ent:1.168Sun Feb 22 15:26:48 2004 +++ phpdoc/entities/global.ent Mon Feb 23 12:37:07 2004 @@ -1,6 +1,6 @@
[PHP-DOC] cvs: livedocs / mkindex.php
didou Mon Feb 23 12:35:31 2004 EDT
Modified files:
/livedocs mkindex.php
Log:
this one was renamed
http://cvs.php.net/diff.php/livedocs/mkindex.php?r1=1.17&r2=1.18&ty=u
Index: livedocs/mkindex.php
diff -u livedocs/mkindex.php:1.17 livedocs/mkindex.php:1.18
--- livedocs/mkindex.php:1.17 Mon Feb 16 12:54:59 2004
+++ livedocs/mkindex.phpMon Feb 23 12:35:30 2004
@@ -19,7 +19,7 @@
// | construct an index |
// +--+
//
-// $Id: mkindex.php,v 1.17 2004/02/16 17:54:59 derick Exp $
+// $Id: mkindex.php,v 1.18 2004/02/23 17:35:30 didou Exp $
/* just to be on the safe side */
@@ -31,7 +31,7 @@
$TMPDIR = $argv[3];
if (!is_dir($PHPDOC) || !is_dir($PHPDOC . DIRECTORY_SEPARATOR . $LANG)) {
- echo "Usage: index-phpdoc.php /path/to/phpdoc lang tmp-dir\n";
+ echo "Usage: mkindex.php /path/to/phpdoc lang tmp-dir\n";
exit(1);
}
[PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Migration Appendice
I'll also do up some notes on COM when I return from the next conference (well, actually write some real docs, since what we have now it pretty useless). --Wez. - Original Message - From: "Gabor Hojtsy" <[EMAIL PROTECTED]> To: "Nuno Lopes" <[EMAIL PROTECTED]> Cc: "PHPdev" <[EMAIL PROTECTED]>; "PHPdoc" <[EMAIL PROTECTED]> Sent: Monday, February 23, 2004 6:24 PM Subject: [PHP-DEV] Re: [PHP-DOC] Migration Appendice > > Today I've finished writing the 'Migrating from PHP 4 to PHP 5' appendice. > > I would like you to review it to check if something is missing or incorrect. > > > > As the on-line version is outdated, use livedocs at: > > http://docs.php.net/en/migration5.html > > Seems to be all right. Would be nice to link to places in the manual, > where other new features are documented (SPL, HTML Tidy, SimpleXML, the > new object model). > > Goba > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > >
Re: [PHP-DOC] Migration Appendice
Today I've finished writing the 'Migrating from PHP 4 to PHP 5' appendice. I would like you to review it to check if something is missing or incorrect. As the on-line version is outdated, use livedocs at: http://docs.php.net/en/migration5.html Seems to be all right. Would be nice to link to places in the manual, where other new features are documented (SPL, HTML Tidy, SimpleXML, the new object model). Goba
[PHP-DOC] Migration Appendice
Hi, Today I've finished writing the 'Migrating from PHP 4 to PHP 5' appendice. I would like you to review it to check if something is missing or incorrect. As the on-line version is outdated, use livedocs at: http://docs.php.net/en/migration5.html thanks, Nuno
[PHP-DOC] cvs: phpdoc /en/appendices migration5.xml
nlopess Mon Feb 23 11:31:35 2004 EDT Modified files: /phpdoc/en/appendices migration5.xml Log: first beta release of the migration chapter :) http://cvs.php.net/diff.php/phpdoc/en/appendices/migration5.xml?r1=1.8&r2=1.9&ty=u Index: phpdoc/en/appendices/migration5.xml diff -u phpdoc/en/appendices/migration5.xml:1.8 phpdoc/en/appendices/migration5.xml:1.9 --- phpdoc/en/appendices/migration5.xml:1.8 Thu Feb 19 11:06:55 2004 +++ phpdoc/en/appendices/migration5.xml Mon Feb 23 11:31:34 2004 @@ -1,5 +1,5 @@ - + Migrating from PHP 4 to PHP 5 @@ -70,6 +70,45 @@ Classes must be declared before used. + + + + strrpos and strripos now + use the entire string as a needle + + + + + + +The following example was valid in PHP 4, although it will produce a fatal +error in PHP 5. + + + + Classes must be declared before used + + + + + @@ -189,6 +228,10 @@ closing it + ibase_db_info - Request statistics about a + database + + ibase_drop_db - Drops a database @@ -203,6 +246,10 @@ returns its new value + ibase_maintain_db - Execute a maintenance command + on the database server + + ibase_name_result - Assigns a name to a result set @@ -218,6 +265,14 @@ service manager and returns immediately + ibase_rollback_ret - Rollback transaction and + retain the transaction context + + + ibase_server_info - Request statistics about a + database + + ibase_service_attach - Connect to the service manager @@ -315,6 +370,10 @@ dBase database + dbx_fetch_row - Fetches rows from a query-result + that had the DBX_RESULT_UNBUFFERED flag set + + file_put_contents - Write a string to a file @@ -347,6 +406,10 @@ exif_imagetype + imagefilter - Applies Filter an image using a + custom angle + + imap_getacl - Gets the ACL for a given mailbox @@ -377,6 +440,14 @@ process + pspell_config_data_dir - Change location of + language data files + + + pspell_config_dict_dir - Change location of the + main word list + + setrawcookie - Send a cookie with no url encoding of the value @@ -438,6 +509,39 @@ + + Databases + +There were some changes in PHP 5 regarding databases (MySQL and SQLite). + + +In PHP 5 the MySQL client libraries are not bundled, because of licence +problems and some others. For more information, read the FAQ entry. + + +There is also a new extension, MySQLi (Improved + MySQL), which is designed to work with MySQL 4.1 and above. + + +Since PHP 5, the SQLite extension is +built-in PHP. SQLite is embeddable SQL database engine and is not a +client library used to connect to a big database server (like MySQL or +PostgreSQL). The SQLite library reads and writes directly to and from the +database files on disk. + + + + + New Object Model + +In PHP 5 there is a new Object Model. PHP's handling of objects has been +completely rewritten, allowing for better performance and more features. +Please read http://www.php.net/zend-engine-2.php";>http://www.php.net/zend-engine-2.php +for more info. + +
[PHP-DOC] Re: [PEAR-DOC] Livedocs
Alan Knowles wrote: Having a had quick look at the latest php-livedocs source... basically this line include LIVEDOC_SOURCE . '/style_mapping.php'; probably wants to do: include LIVEDOC_SOURCE . '/'.LIVEDOC_TYPE .'_style_mapping.php'; where LIVEDOC_TYPE = php|pear|php-gtk where pear_style_mapping.php includes php_style_mapping.php as a basis.. Seems good to me. The main modifications where to do with the fact that pear, in some places uses a slightly different tag sequence.. for different parts (a prime example being the methods synopsis. what the build process ? how did you hack livedocs to generate the .sqlite files for peardoc ? didou
[PHP-DOC] Re: [PEAR-DOC] Livedocs
Having a had quick look at the latest php-livedocs source... basically this line include LIVEDOC_SOURCE . '/style_mapping.php'; probably wants to do: include LIVEDOC_SOURCE . '/'.LIVEDOC_TYPE .'_style_mapping.php'; where LIVEDOC_TYPE = php|pear|php-gtk where pear_style_mapping.php includes php_style_mapping.php as a basis.. The main modifications where to do with the fact that pear, in some places uses a slightly different tag sequence.. for different parts (a prime example being the methods synopsis. Regards Alan Mehdi Achour wrote: Hartmut Holzgraefe wrote: Alan Knowles wrote: I forked an early version about 4 months ago.. - see the archives for more details on it's status.. please, no more forking of doc-related tools :( this is not the current goal ;) If Alan's fork is good for livedocs, we'll see how to change livedocs to compile for PHP or PEAR documentation. it will be a setting for the ./configure line I think (--with-build-type=[php|pear]doc) didou -- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.com
[PHP-DOC] cvs: phpdoc /en/faq databases.xml
nlopess Mon Feb 23 10:38:39 2004 EDT Modified files: /phpdoc/en/faq databases.xml Log: better docbook tag and livedocs compliance http://cvs.php.net/diff.php/phpdoc/en/faq/databases.xml?r1=1.23&r2=1.24&ty=u Index: phpdoc/en/faq/databases.xml diff -u phpdoc/en/faq/databases.xml:1.23 phpdoc/en/faq/databases.xml:1.24 --- phpdoc/en/faq/databases.xml:1.23Sat Dec 20 23:21:40 2003 +++ phpdoc/en/faq/databases.xml Mon Feb 23 10:38:38 2004 @@ -1,5 +1,5 @@ - + Database issues Database issues @@ -59,13 +59,15 @@ built in drivers), or to use an intermediary file format that Access and PHP both understand, such as flat files or dBase databases. On this point Tim Hayes from OpenLink software writes: - - Using another database as an intermediary is not a good idea, when you can - use ODBC from PHP straight to your database - i.e. with OpenLink's drivers. If - you do need to use an intermediary file format, OpenLink have now released - Virtuoso (a virtual database engine) for NT, Linux and other Unix platforms. - Please visit our website for a free download. - + + +Using another database as an intermediary is not a good idea, when you can +use ODBC from PHP straight to your database - i.e. with OpenLink's drivers. If +you do need to use an intermediary file format, OpenLink have now released +Virtuoso (a virtual database engine) for NT, Linux and other Unix platforms. +Please visit our website for a free download. + + One option that has proved successful is to use MySQL and its
Re: [PHP-DOC] Re: [PEAR-DOC] Livedocs
If someone will give me the lowdown on the way OO is being treated in phpdoc I'll spend some time bringing php-gtk-doc into line. So long as it's not about to all change again. If there would be a consensus I would be happy to provide details. Goba
[PHP-DOC] Re: [PEAR-DOC] Livedocs
Hartmut Holzgraefe wrote: Alan Knowles wrote: I forked an early version about 4 months ago.. - see the archives for more details on it's status.. please, no more forking of doc-related tools :( this is not the current goal ;) If Alan's fork is good for livedocs, we'll see how to change livedocs to compile for PHP or PEAR documentation. it will be a setting for the ./configure line I think (--with-build-type=[php|pear]doc) didou
RE: [PHP-DOC] Re: [PEAR-DOC] Livedocs
If someone will give me the lowdown on the way OO is being treated in phpdoc I'll spend some time bringing php-gtk-doc into line. So long as it's not about to all change again. - Steph > -Original Message- > From: Hartmut Holzgraefe [mailto:[EMAIL PROTECTED] > Sent: 23 February 2004 14:51 > To: Alan Knowles > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Mehdi Achour > Subject: [PHP-DOC] Re: [PEAR-DOC] Livedocs > > > Alan Knowles wrote: > > I forked an early version about 4 months ago.. - see the archives for > > more details on it's status.. > > please, no more forking of doc-related tools :( > > the current situation with pear-doc and php-gtk-doc using versions > of phpdoc forked off in a very distant past and heavily being > modified ever since are already an unnecessary nightmare ... > > -- > Hartmut Holzgraefe <[EMAIL PROTECTED]>
[PHP-DOC] Re: [PEAR-DOC] Livedocs
Alan Knowles wrote: I forked an early version about 4 months ago.. - see the archives for more details on it's status.. please, no more forking of doc-related tools :( the current situation with pear-doc and php-gtk-doc using versions of phpdoc forked off in a very distant past and heavily being modified ever since are already an unnecessary nightmare ... -- Hartmut Holzgraefe <[EMAIL PROTECTED]>
[PHP-DOC] Re: [PEAR-DOC] Livedocs
I forked an early version about 4 months ago.. - see the archives for more details on it's status.. The mappings in phpdoc (eg. elements->html are not totally suitable for pear..) - they need changing a little - I cant remember the other changes I had to do... but there where quite a few bug fixes to get it to parse and display some of pear.. (eg. there was quite a few missing htmlspecialchars in the early versions) http://devel.akbkhome.com/livedocs/livedoc.php The source is here http://devel.akbkhome.com/svn/index.php/akpear/LiveDocs/ pear source normally parses with xlst perfectly ok - which generates the index sql. I'm unlikely to carry on much maintenence on the code (it just about works enough for me to test my own parts of the manual)... and I'm still a bit busy on other stuff.. Regards Alan This is also the plan of phpdoc'ers (cc'ed). We have already splitted the livedocs rendering magic to allow the choice of a particular theme, with custom plugins. I was asking here to see if someone have started the work. I'd like to see how the build part will be splitted to manage both pear and php documentation. didou
[PHP-DOC] Re: [PEAR-DOC] Livedocs
Lukas Smith wrote: Martin Jansen wrote: On Mon Feb 23, 2004 at 02:3617PM +0100, Lukas Smith wrote: Mehdi Achour wrote: Is there a plan to use livedocs for the PEAR manual build one day ? If so, did someone start the work ? Well it has been discussed on various occations, but currently I am not aware of any concrete plans, nor of any serious attempts at using Livedocs for the PEAR Manual. I am not sure how much of an effort it really is to get peardoc2 to work with Livedocs. Anyways I would be so happy if we finally did get this up and running. I do not see the advantage of using Livedocs on pear.php.net. The way I got it all changes to the manual would be more or less immediatly available. Sounds like a huge advantage alone. Also it doesnt require so many exotic tools. Actually I was hoping to have sort of a wiki style interface someday to further ease fixing of little typos. This is also the plan of phpdoc'ers (cc'ed). We have already splitted the livedocs rendering magic to allow the choice of a particular theme, with custom plugins. I was asking here to see if someone have started the work. I'd like to see how the build part will be splitted to manage both pear and php documentation. didou
Re: [PHP-DOC] security chapter - my fault
On Mon, 23 Feb 2004, Serban Gh. Ghita wrote: > Mr Derick Rethans notified my that i have messed by mistake the security > chapter under the /phpdoc/ tree. nope, you didn't change things in the phpdoc tree, but in the root of the CVS server. No harm done. > I did not do that on purpose, and please excuse me for what i have done. Now > i want to know if that can be fixed. I insist to phpdoc (en) maintainers to > add some explicit examples of cvs operations (update, commit, checkout, > etc.). I think the cvs is very tricky even for the ones who read the > manual.. I think we already have this in the dochowto...: http://nl3.php.net/manual/howto/chapter-cvs.html regards, Derick
[PHP-DOC] security chapter - my fault
Hello, Mr Derick Rethans notified my that i have messed by mistake the security chapter under the /phpdoc/ tree. I did not do that on purpose, and please excuse me for what i have done. Now i want to know if that can be fixed. I insist to phpdoc (en) maintainers to add some explicit examples of cvs operations (update, commit, checkout, etc.). I think the cvs is very tricky even for the ones who read the manual.. Best regards, Serban Gh. Ghita
[PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions fwrite.xml
irchtml Mon Feb 23 03:09:32 2004 EDT
Modified files:
/phpdoc/en/reference/filesystem/functions fwrite.xml
Log:
updated example (per user note)
http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/fwrite.xml?r1=1.8&r2=1.9&ty=u
Index: phpdoc/en/reference/filesystem/functions/fwrite.xml
diff -u phpdoc/en/reference/filesystem/functions/fwrite.xml:1.8
phpdoc/en/reference/filesystem/functions/fwrite.xml:1.9
--- phpdoc/en/reference/filesystem/functions/fwrite.xml:1.8 Mon Dec 15 11:49:45
2003
+++ phpdoc/en/reference/filesystem/functions/fwrite.xml Mon Feb 23 03:09:31 2004
@@ -1,5 +1,5 @@
-
+
@@ -62,7 +62,7 @@
}
// Write $somecontent to our opened file.
-if (!fwrite($handle, $somecontent)) {
+if (fwrite($handle, $somecontent) === FALSE) {
echo "Cannot write to file ($filename)";
exit;
}
