Re: [PHP-DOC] Documenting configure options/Updating and splittinginstall.configure.php
So you disagree with separate lists for separate commits. Are you interested in it, ja, kr or ru commits? IMHO no. Are you interested You are right. But I see the problem of discussions starting on lets say the German part and nobody who is not reading the German list will notice it. in discussions like this? IMHO yes. So then you would sucsribe to the main (en) list with general language independent discussions, and en commits, and to your own list... You are not interested in changes, updates in the hu tree, and discussion in Hungarian... If the discussion is about langos, well I am very interested ;) Well, from inside, I see that even while PHP is very good documented, there are many things we can advance our manual. ACK. IMHO this would be good for a pro too. The question is who we call a pro. If you are a pro at dinamic website programming but have not worked with gd images before, you will find this type of index useful, as you'll find Image creation, Text on image functions, ... categories useful. Well you can say in that case, that person is a newbie for images, so he is a newbie :)) You are right. Yes, you can start off with creating phpdoc/en/configure IMHO, so people will be able to contribute, and translate as soon as it will be ready for inclusion in the manual. I was in a meeting yesterday with Egon and Georg, and we will start right in config.xml. So please don't wonder, if it changes often ;) I hope he will read our mails when he get back ;) That is for sure. Mark
[PHP-DOC] cvs: phpdoc /it/functions array.xml
eschmid Fri Dec 28 04:21:02 2001 EDT Modified files: /phpdoc/it/functionsarray.xml Log: Fixed a end tag. Index: phpdoc/it/functions/array.xml diff -u phpdoc/it/functions/array.xml:1.37 phpdoc/it/functions/array.xml:1.38 --- phpdoc/it/functions/array.xml:1.37 Wed Dec 26 07:06:48 2001 +++ phpdoc/it/functions/array.xml Fri Dec 28 04:21:02 2001 @@ -140,7 +140,7 @@ /para para Vedere anche: functionlist/function, - functionlist/function, e functionrange/function + functionlist/function, e functionrange/function /para /refsect1 /refentry
[PHP-DOC] Re: [PHP-DEV] Proposed patch for /php4/win32/install.txt
On Friday 28 December 2001 2:03 am, James Cox wrote: Since the url specified for browscap.ini is dead, and i can't find a cached version, i am proposing a patch to remove the link (And assoc. text) from the page. To the best of my knowledge, install.txt is now built by a script which generates it from the installation page in the manual. I've CC'd this to the doc list where, I'm sure, someone will correct me if I'm wrong. If I'm correct, you need to patch the manual page. Cheers -- Phil Driscoll
[PHP-DOC] cvs: phpdoc /en/functions pcre.xml xmlrpc.xml
gobaFri Dec 28 07:44:29 2001 EDT
Modified files:
/phpdoc/en/functionspcre.xml xmlrpc.xml
Log:
Correct errors reported by Saxon
Index: phpdoc/en/functions/pcre.xml
diff -u phpdoc/en/functions/pcre.xml:1.67 phpdoc/en/functions/pcre.xml:1.68
--- phpdoc/en/functions/pcre.xml:1.67 Wed Dec 12 15:47:14 2001
+++ phpdoc/en/functions/pcre.xmlFri Dec 28 07:44:29 2001
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.67 $ --
+!-- $Revision: 1.68 $ --
reference id=ref.pcre
titleRegular Expression Functions (Perl-Compatible)/title
titleabbrevPCRE/titleabbrev
@@ -647,7 +647,7 @@
used delimiter./para
para
The special regular expression characters are:
- screen. \\ + * ? [ ^ ] $ ( ) { } = ! | :/screen
+ screen. \\ + * ? [ ^ ] $ ( ) { } = ! lt; gt; | :/screen
/para
para
example
Index: phpdoc/en/functions/xmlrpc.xml
diff -u phpdoc/en/functions/xmlrpc.xml:1.2 phpdoc/en/functions/xmlrpc.xml:1.3
--- phpdoc/en/functions/xmlrpc.xml:1.2 Fri Dec 21 08:28:42 2001
+++ phpdoc/en/functions/xmlrpc.xml Fri Dec 28 07:44:29 2001
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.2 $ --
+!-- $Revision: 1.3 $ --
reference id=ref.xmlrpc
titleXMLRPC functions/title
titleabbrevXMLRPC function/titleabbrev
@@ -55,7 +55,7 @@
refentry id=function.xmlrpc-decode-request
refnamediv
refnamexmlrpc_decode_request/refname
-refpurpose method [, string encoding]) Decodes XML into native PHP types
/refpurpose
+refpurposeDecodes XML into native PHP types /refpurpose
/refnamediv
refsect1
titleDescription/title
@@ -63,7 +63,10 @@
funcprototype
funcdefarray functionxmlrpc_decode_request/function/funcdef
paramdefstring parameterxml/parameter/paramdef
- paramdefstring parameter/parameter/paramdef
+ paramdefstring parametermethod/parameter/paramdef
+ paramdefstring
+ parameteroptionalencoding/optional/parameter
+ /paramdef
/funcprototype
/funcsynopsis
warn.experimental.func;
[PHP-DOC] used tags in docbook XML files
Hi! I have just committed a script to check what DocBook XML tags we use, and what are only used once or twice (like formalpara). The results are interesting... IMHO this list would alos help to make some standard for used tags, and don't let everybody invent his/her own tag usage style. If we use a small subset of tags, people can easily identify what tag means what... Using exotic tags like formalpara may lead to confusion for authors, and new contributors. The text file sent is a test on the en XML tree. Goba TAG USAGE STATISCTICS = In this file you can find tag usage stats compiled from the following tree[s] at phpdoc: en. You may find some rarely used tags here, and find out what tags others use to write documentation. = function 10168 parameter 8434 para 7294 paramdef 5147 title 3889 entry 3357 simpara2726 refsect1 2583 refnamediv 2577 refentry 2577 refname2577 refpurpose 2577 funcdef2570 funcprototype 2570 funcsynopsis 2560 listitem 1939 literal1330 row1155 programlisting 1073 link 903 optional 811 example699 term 489 varlistentry 489 note 399 informalexample332 ulink 306 filename 259 member 219 type 216 itemizedlist 213 ?xml 158 emphasis 155 varname150 sect1 148 sect2 146 titleabbrev123 reference 110 partintro 102 constant 98 replaceable96 acronym88 answer 82 qandaentry 82 question 82 tgroup 72 tbody 72 variablelist 70 table 68 screen 61 thead 59 warning57 command54 option 51 literallayout 39 chapter36 section29 simplelist 18 refsect2 17 orderedlist17 sect3 16 systemitem 14 errortype 14 qandaset 13 productname12 envar 12 computeroutput 11 firstname 10 appendix 10 userinput 10 caution10 surname10 author 8 classname 8 abbrev 7 tip6 sgmltag6 glossterm 5 synopsis 5 year 5 informaltable 4 sect4 3 editor 2 manvolnum 2 refentrytitle 2 authorgroup2 refsynopsisdiv 2 citerefentry 2 blockquote 2 application2 holder 1 bookinfo 1 pubdate1 symbol 1 copyright 1 abstract 1 errorcode 1 prompt 1 citation 1 preface1 legalnotice1 footnoteref1 footnote 1 formalpara 1
[PHP-DOC] Bug #14732 Updated: Broken links in global.ent
ID: 14732 Updated by: goba Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Documentation problem Operating System: all PHP Version: 4.1.1 New Comment: Please commit that little script into phpdoc into the scripts directory. We have some scripts there to test XML files, such as the entities.php or dbtags.php. It would be nice to make this test from time to time. To answer your current bug report, I have not time currently to skim through these addresses and find the right, so anybody with sufficient time, or who knows some of the right links would be welcome :) -- Goba Previous Comments: [2001-12-28 08:04:05] [EMAIL PROTECTED] Hi, just wrote a little script and checked global.ent url.adabas: unknown host (www.adabas.com) url.hyperwave-proto: document not found (http://www.hyperwave.de/7.17-hg-prot) url.iicm: unknown host (iicm.edu) url.iptc: document not found or unreachable (http://www.iptc.org/) url.ldap.ldapworld: document not found or unreachable (http://elvira.innosoft.com/ldapworld) url.libiconv: document not found (http://clisp.cons.org/~haible/packages-libiconv.html) url.malinimg: document not found (http://www.pvv.org/~ssb/malin/bilder/mi/twain001.jpg) url.mersenne.twister: unknown host (www.scp.syr.edu) url.nis: document not found (http://www.desy.de/~sieversm/ypdoku/ypdoku/ypdoku.html) Georg Edit this bug report at http://bugs.php.net/?id=14732edit=1
[PHP-DOC] Bug #14734 Updated: new superglobals ($_SERVER, etc.) not documented
ID: 14734 Updated by: mfischer Reported By: [EMAIL PROTECTED] Old Summary: default HTTP vars and PHP_SELF not available Old Status: Bogus Status: Open Old Bug Type: Scripting Engine problem Bug Type: Documentation problem Operating System: Win XP PHP Version: 4.1.0 New Comment: Valid point. I'm reopening this as a documentation problem. Previous Comments: [2001-12-28 10:01:35] [EMAIL PROTECTED] Hi All, Thanks for the replies. The docs tell me that using globally registered vars presents a security risk and is being turned off in future versions anyway, so it's quite necessary to get accustomed to it. Using $_SERVER['PHP_SELF'] must be the way to go. However, where to find proper documentation on these 'new' vars ? I can't find them, only some pages mentioning they exist.. [2001-12-28 09:56:13] [EMAIL PROTECTED] The correct way would be to use $_SERVER['PHP_SELF'] ; this is guaranteed to work with and without register_globals = off. [2001-12-28 09:34:57] [EMAIL PROTECTED] Then don't turn register_globals off. Turning off register_globals gets rid of all the globals. If you still want some, leave it turned on, but simply set your variables_order directive in your php.ini file to reflect which globals you want. For example, if you want environment and server variables, set it to ES [2001-12-28 09:31:19] [EMAIL PROTECTED] When using PHP with track_vars On and register_globals Off (recommended setting), PHP doesn't know the built-in system and environment vars anymore. For example, $PHP_SELF becomes and unknow variable. This is really annoying. Edit this bug report at http://bugs.php.net/?id=14734edit=1
[PHP-DOC] cvs: phpdoc /en/appendices commandline.xml
gobaFri Dec 28 10:14:25 2001 EDT Modified files: /phpdoc/en/appendices commandline.xml Log: Add -f and -l option documentation. Add see also readline para. Index: phpdoc/en/appendices/commandline.xml diff -u phpdoc/en/appendices/commandline.xml:1.7 phpdoc/en/appendices/commandline.xml:1.8 --- phpdoc/en/appendices/commandline.xml:1.7Wed Dec 12 15:46:26 2001 +++ phpdoc/en/appendices/commandline.xmlFri Dec 28 10:14:25 2001 @@ -1,12 +1,12 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.7 $ -- +!-- $Revision: 1.8 $ -- !-- TODO: The command line options not in the list, but in the -h output below: - -f, -e, -z, -l + -e, -z It would be best to document these, and collect more info about -c and -d! @@ -95,6 +95,14 @@ /entry /row row + entry-f/entry + entry + Parse the file given, and search for syntactical and + fatal errors. This option implies -q. Use for + debugging purposes. + /entry + /row + row entry-v/entry entry By calling PHP with this option, you can ask @@ -130,6 +138,16 @@ /entry /row row + entry-l/entry + entry + Check the file given for syntax errors. This + option implies -q. Use for debugging purpouses. + This option won't find fatal errors (like undefined + functions). Use -f if you would like to test + for fatal errors too. + /entry + /row + row entry-m/entry entry Using this option, PHP prints out the built in @@ -239,6 +257,11 @@ will run it for you with your added options: literalscript.bat echothis/literal or literalscript.bat -h/literal. + /para + para + See also the link linkend=ref.readlineReadline/link + extension documentation for more functions you can use + to enhance your command line applications in PHP. /para /appendix
[PHP-DOC] Bug #14734 Updated: new superglobals ($_SERVER, etc.) not documented
ID: 14734 Updated by: goba Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Documentation problem Operating System: Win XP PHP Version: 4.1.0 New Comment: Just a note: in the PHP 4.1.0 phpinfo() output, all the predefined vars are printed as _SERVER and _ENV members, except PHP_SELF, it is printed alone, and not in any array. This must be corrected! Previous Comments: [2001-12-28 10:05:28] [EMAIL PROTECTED] Valid point. I'm reopening this as a documentation problem. [2001-12-28 10:01:35] [EMAIL PROTECTED] Hi All, Thanks for the replies. The docs tell me that using globally registered vars presents a security risk and is being turned off in future versions anyway, so it's quite necessary to get accustomed to it. Using $_SERVER['PHP_SELF'] must be the way to go. However, where to find proper documentation on these 'new' vars ? I can't find them, only some pages mentioning they exist.. [2001-12-28 09:56:13] [EMAIL PROTECTED] The correct way would be to use $_SERVER['PHP_SELF'] ; this is guaranteed to work with and without register_globals = off. [2001-12-28 09:34:57] [EMAIL PROTECTED] Then don't turn register_globals off. Turning off register_globals gets rid of all the globals. If you still want some, leave it turned on, but simply set your variables_order directive in your php.ini file to reflect which globals you want. For example, if you want environment and server variables, set it to ES [2001-12-28 09:31:19] [EMAIL PROTECTED] When using PHP with track_vars On and register_globals Off (recommended setting), PHP doesn't know the built-in system and environment vars anymore. For example, $PHP_SELF becomes and unknow variable. This is really annoying. Edit this bug report at http://bugs.php.net/?id=14734edit=1
[PHP-DOC] cvs: phpdoc /ja/appendices commandline.xml
fujimotoFri Dec 28 10:28:03 2001 EDT Modified files: /phpdoc/ja/appendices commandline.xml Log: updated translation. Index: phpdoc/ja/appendices/commandline.xml diff -u phpdoc/ja/appendices/commandline.xml:1.4 phpdoc/ja/appendices/commandline.xml:1.5 --- phpdoc/ja/appendices/commandline.xml:1.4Wed Dec 12 15:52:13 2001 +++ phpdoc/ja/appendices/commandline.xmlFri Dec 28 10:28:02 2001 @@ -1,12 +1,12 @@ ?xml version=1.0 encoding=utf-8? -!-- $Revision: 1.4 $ -- +!-- $Revision: 1.5 $ -- !-- TODO: The command line options not in the list, but in the -h output below: - -f, -e, -z, -l + -e, -z It would be best to document these, and collect more info about -c and -d! @@ -88,6 +88,14 @@ /entry /row row + entry-f/entry + entry + +与えられたファイルを解析し、文法上のミスや致命的なエラー +を探します。このオプションが指定されると自動的に -q +が + +指定されたものと見なされます。デバッグに使用してください。 + /entry + /row + row entry-v/entry entry このオプションを付けてPHPをコールすると、バージョン番号、すな @@ -120,6 +128,16 @@ /entry /row row + entry-l/entry + entry + +与えられたファイルの文法をチェックします。このオプションが +指定されると自動的に -q +も指定されたものと見なされます。 + +デバッグに使用してください。このオプションでは(定義されて + +いない関数といった)致命的なエラーを探し出すことはしません。 +致命的なエラーも探し出したい場合は -f +を使用してください。 + /entry + /row + row entry-m/entry entry このオプションにより、組み込まれた(そしてロードされた)PHPモジュー @@ -223,6 +241,11 @@ あるとするとこのバッチファイルはliteralscript.bat echothis/literal もしくはliteralscript.bat -h/literalといったオプションを追加して 実行することが出来ます。 + /para + para + +コマンドラインで動作するPHPアプリケーションを書く際に有用となる関数に + ついてはlink linkend=ref.readlineReadline/link拡張モジュールの + ドキュメントを参照してください。 /para /appendix
[PHP-DOC] cvs: phpdoc /ja/functions zlib.xml
fujimotoFri Dec 28 10:30:22 2001 EDT
Modified files:
/phpdoc/ja/functionszlib.xml
Log:
updated translation.
Index: phpdoc/ja/functions/zlib.xml
diff -u phpdoc/ja/functions/zlib.xml:1.14 phpdoc/ja/functions/zlib.xml:1.15
--- phpdoc/ja/functions/zlib.xml:1.14 Wed Dec 12 15:53:54 2001
+++ phpdoc/ja/functions/zlib.xmlFri Dec 28 10:30:21 2001
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=utf-8?
-
+!-- $Revision: 1.15 $ --
reference id=ref.zlib
titlezlib圧縮関数/title
titleabbrevZlib/titleabbrev
@@ -16,6 +16,19 @@
link linkend=ref.filesystemfilesystem/link 関数を含んでいます。
(非圧縮のファイルも使用可能ですが、ソケットは使用できません)
/para
+ note
+para
+
+バージョン4.0.4-devで.gzファイルに対応したfopen-wrapperを導入しました。
+ これによりfunctionfopen/functionに'zlib:'をプレフィクスとした
+
+ファイル名又はパス名を渡すことで、通常のf*()関数で圧縮されたファイルに
+ 透過的にアクセスすることが出来ます。
+/para
+para
+
+この機能を利用するにはliteralfopencookie()/literal関数を提供する
+
+Cのランタイムライブラリが必要です。現在私の知る限りでは、GNU
+ libcが
+ この機能を提供する唯一のライブラリです。
+/para
+ /note
sect1 id=zlib-example
title簡単なコードの例/title
@@ -26,9 +39,10 @@
example
title簡単な Zlib の例/title
programlisting role=php
-lt;?php
+![CDATA[
+?php
$filename = tempnam ('/tmp', 'zlibtest').'.gz';
-print lt;html\nlt;headlt;/head\nlt;body\nlt;pre\n;
+print html\nhead/head\nbody\npre\n;
$s = Only a test, test, test, test, test, test, test, test!\n;
// 最大限の圧縮を指定して書きこみ用にファイルをオープン
$zp = gzopen ($filename, w9);
@@ -48,8 +62,9 @@
echo Error with zlib functions!;
}
unlink ($filename);
-print lt;/pre\nlt;/h1lt;/body\nlt;/html\n;
+print /pre\n/h1/body\n/html\n;
?
+]]
/programlisting
/example
/sect1
@@ -265,9 +280,7 @@
paramdefstring parameterfilename/parameter/paramdef
paramdefstring parametermode/parameter/paramdef
paramdefint
- parameter
- replaceableoptionaluse_include_path/optional/replaceable
- /parameter
+ parameteroptionaluse_include_path/optional/parameter
/paramdef
/funcprototype
/funcsynopsis
@@ -282,7 +295,7 @@
説明を参照下さい。)
/para
para
- Gzopen
は、gzipフォーマットでないファイルの読み込みについても
+ gzopen
+は、gzipフォーマットでないファイルの読み込みについても
使用することができます。
この場合、functiongzread/functionは、ファイルを解凍せずに直接読み
込まれます。
@@ -304,7 +317,9 @@
example
titlefunctiongzopen/functionの例/title
programlisting role=php
+![CDATA[
$fp = gzopen (/tmp/file.gz, r);
+]]
/programlisting
/example
/para
@@ -399,11 +414,13 @@
para
informalexample
programlisting role=php
+![CDATA[
// gz ファイルの内容を文字列に読み込みます
$filename = /usr/local/something.txt.gz;
-$zd = gzopen ( $filename, r );
-$contents = gzread ( $zd, 1 );
-gzclose ( $zd );
+$zd = gzopen ($filename, r);
+$contents = gzread ($zd, 1);
+gzclose ($zd);
+]]
/programlisting
/informalexample
/para
@@ -551,7 +568,7 @@
引数parameterlength/parameterが指定された場合、
link linkend=ini.magic-quotes-runtimemagic_quotes_runtime/link
設定オプションは無視されて parameterstring/parameter から
- ィéッシュが取り除かれなくなることに注意してください。
+ スラッシュが取り除かれなくなることに注意してください。
/simpara
simpara
functiongzread/function、functiongzopen/function、
@@ -776,13 +793,15 @@
example
titlegzipファイルを作成する/title
programlisting role=php
-lt;?php
+![CDATA[
+?php
$data = implode(, bigfile.txt);
$gzdata = gzencode($data, 9);
$fp = fopen(bigfile.txt.gz, w);
fwrite($fp, $gzdata);
fclose($fp);
-?gt;
+?
+]]
/programlisting
/example
/para
[PHP-DOC] cvs: phpdoc / global.ent
georg Fri Dec 28 10:30:32 2001 EDT Modified files: /phpdoc global.ent Log: fixed broken links for adabas, ldap, libiconv Index: phpdoc/global.ent diff -u phpdoc/global.ent:1.133 phpdoc/global.ent:1.134 --- phpdoc/global.ent:1.133 Sat Dec 22 07:44:48 2001 +++ phpdoc/global.ent Fri Dec 28 10:30:32 2001 @@ -1,11 +1,11 @@ !-- -*- SGML -*- - $Id: global.ent,v 1.133 2001/12/22 12:44:48 georg Exp $ + $Id: global.ent,v 1.134 2001/12/28 15:30:32 georg Exp $ Contains global macros for all the XML documents. -- -!ENTITY url.adabas http://www.adabas.com/; +!ENTITY url.adabas http://www.software-ag.com/adabasd/; !ENTITY url.adobe http://www.adobe.com/; !ENTITY url.adobe.acrobat http://www.adobe.com/products/acrobat/readstep.html; !ENTITY url.apache http://www.apache.org/; @@ -74,11 +74,11 @@ !ENTITY url.ldap.netscape http://developer.netscape.com/tech/directory/; !ENTITY url.ldap.filters http://developer.netscape.com/docs/manuals/directory/41/ag/find.htm; !ENTITY url.ldap.michigan http://www.umich.edu/~dirsvcs/ldap/index.html; -!ENTITY url.ldap.ldapworld http://elvira.innosoft.com/ldapworld; +!ENTITY url.ldap.ldapworld http://www.innosoft.com/ldapworld; !ENTITY url.ldap.openldap http://www.openldap.org/; !ENTITY url.ldap.openldap-c-api http://www.openldap.org/devel/cvsweb.cgi/~checkout~/doc/drafts/draft-ietf-ldapext-ldap-c-api-xx.txt; !ENTITY url.levenshtein.demo http://odur.let.rug.nl/~kleiweg/lev/; -!ENTITY url.libiconv http://clisp.cons.org/~haible/packages-libiconv.html; +!ENTITY url.libiconv http://www.gnu.org/software/libiconv/; !ENTITY url.macosx http://www.entropy.ch/software/macosx; !ENTITY url.macosx2 http://www.access.ch/ml/; !ENTITY url.macromedia http://www.macromedia.com/;
[PHP-DOC] coding standards - draft
Hi, in reference to the thread [PHP-DOC] MySQL examples need review started by Slawomir Pucia: I gathered the suggestions made by the people, put the relevant pieces from the current howto, added PEAR Coding standards and some suggestions of mine to a working draft for coding standards. Its far away from beeing perfect, but maybe a starting point for further discussion. Interested people can download the draft (simple text-file) at http://www.holliwell.de/draft/draft.tar.gz; (it's about 3 kb) or view online: http://www.holliwell.de/draft/draft Friedhelm
[PHP-DOC] Bug #14734 Updated: new superglobals ($_SERVER, etc.) not documented
ID: 14734 Updated by: mfischer Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Documentation problem Operating System: Win XP PHP Version: 4.1.0 New Comment: It's printed in _SERVER too (apache 1.3.22/php 4.1.0). Previous Comments: [2001-12-28 10:17:17] [EMAIL PROTECTED] Just a note: in the PHP 4.1.0 phpinfo() output, all the predefined vars are printed as _SERVER and _ENV members, except PHP_SELF, it is printed alone, and not in any array. This must be corrected! [2001-12-28 10:05:28] [EMAIL PROTECTED] Valid point. I'm reopening this as a documentation problem. [2001-12-28 10:01:35] [EMAIL PROTECTED] Hi All, Thanks for the replies. The docs tell me that using globally registered vars presents a security risk and is being turned off in future versions anyway, so it's quite necessary to get accustomed to it. Using $_SERVER['PHP_SELF'] must be the way to go. However, where to find proper documentation on these 'new' vars ? I can't find them, only some pages mentioning they exist.. [2001-12-28 09:56:13] [EMAIL PROTECTED] The correct way would be to use $_SERVER['PHP_SELF'] ; this is guaranteed to work with and without register_globals = off. [2001-12-28 09:34:57] [EMAIL PROTECTED] Then don't turn register_globals off. Turning off register_globals gets rid of all the globals. If you still want some, leave it turned on, but simply set your variables_order directive in your php.ini file to reflect which globals you want. For example, if you want environment and server variables, set it to ES 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/?id=14734 Edit this bug report at http://bugs.php.net/?id=14734edit=1
[PHP-DOC] Bug #14732 Updated: Broken links in global.ent
ID: 14732 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Documentation problem Operating System: all PHP Version: 4.1.1 New Comment: broken links fixed for - adabas - ldap - libiconv Previous Comments: [2001-12-28 09:55:54] [EMAIL PROTECTED] Please commit that little script into phpdoc into the scripts directory. We have some scripts there to test XML files, such as the entities.php or dbtags.php. It would be nice to make this test from time to time. To answer your current bug report, I have not time currently to skim through these addresses and find the right, so anybody with sufficient time, or who knows some of the right links would be welcome :) -- Goba [2001-12-28 08:04:05] [EMAIL PROTECTED] Hi, just wrote a little script and checked global.ent url.adabas: unknown host (www.adabas.com) url.hyperwave-proto: document not found (http://www.hyperwave.de/7.17-hg-prot) url.iicm: unknown host (iicm.edu) url.iptc: document not found or unreachable (http://www.iptc.org/) url.ldap.ldapworld: document not found or unreachable (http://elvira.innosoft.com/ldapworld) url.libiconv: document not found (http://clisp.cons.org/~haible/packages-libiconv.html) url.malinimg: document not found (http://www.pvv.org/~ssb/malin/bilder/mi/twain001.jpg) url.mersenne.twister: unknown host (www.scp.syr.edu) url.nis: document not found (http://www.desy.de/~sieversm/ypdoku/ypdoku/ypdoku.html) Georg Edit this bug report at http://bugs.php.net/?id=14732edit=1
[PHP-DOC] cvs: phpdoc /de/functions datetime.xml
drews Fri Dec 28 11:43:41 2001 EDT Modified files: /phpdoc/de/functionsdatetime.xml Log: added W-format option Index: phpdoc/de/functions/datetime.xml diff -u phpdoc/de/functions/datetime.xml:1.22 phpdoc/de/functions/datetime.xml:1.23 --- phpdoc/de/functions/datetime.xml:1.22 Wed Dec 12 15:46:08 2001 +++ phpdoc/de/functions/datetime.xmlFri Dec 28 11:43:40 2001 @@ -211,6 +211,12 @@ /listitem listitem simpara + W - ISO-8601 Wochennummer des Jahres (Woche beginnt mit Montag) + (seit PHP 4.1.0) + /simpara + /listitem + listitem + simpara Y - Jahr als vierstellige Zahl, z.B. 1999 /simpara /listitem
[PHP-DOC] cvs: phpdoc /en/functions datetime.xml
drews Fri Dec 28 11:45:39 2001 EDT Modified files: /phpdoc/en/functionsdatetime.xml Log: added W-format option Index: phpdoc/en/functions/datetime.xml diff -u phpdoc/en/functions/datetime.xml:1.59 phpdoc/en/functions/datetime.xml:1.60 --- phpdoc/en/functions/datetime.xml:1.59 Wed Dec 19 09:01:43 2001 +++ phpdoc/en/functions/datetime.xmlFri Dec 28 11:45:39 2001 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.59 $ -- +!-- $Revision: 1.60 $ -- reference id=ref.datetime titleDate and Time functions/title titleabbrevDate/time/titleabbrev @@ -223,6 +223,12 @@ listitem simpara w - day of the week, numeric, i.e. 0 (Sunday) to 6 +(Saturday) + /simpara + /listitem + listitem + simpara +W - ISO-8601 week number of year, weeks starting on monday (added in PHP +4.1.0) (Saturday) /simpara /listitem
Re: [PHP-DOC] coding standards - draft
I gathered the suggestions made by the people, put the relevant pieces
from the current howto, added PEAR Coding standards and some
suggestions of mine to a working draft for coding standards. Its far
away from beeing perfect, but maybe a starting point for further
discussion.
Interested people can download the draft (simple text-file) at
http://www.holliwell.de/draft/draft.tar.gz; (it's about 3 kb)
or view online: http://www.holliwell.de/draft/draft
Nice. Some additions:
- function naming: whether we use fooFunction() or foo_function()
in functions defined in examples (if more than one word needed)
I prefere the php form foo_function()
- or die is good for development, but useless for production,
use some user defined exit function instead on error
- use ${varname} for complex vars in strings, $varname[x]
will confuse readers, as this is illegal outside strings,
concatenation makes code unreadable
- do not use phpdoc (PEAR) comments, like @param
- example email addresses, like [EMAIL PROTECTED]
(someone pointed out the many junk mail coming
to [EMAIL PROTECTED] and the like caused by an
example on the mail function page)
- For short example printouts, use a C++ style comment
on the line where the output occurs, or the next line,
where it is needed:
echo $var; // outputs: 32
In this case, using a separate screen would just
clutter things...
- Do not take advantage of register_globals, just in
case you would like to present what register_globals
means
- If you use new vars (like $_ENV), always note that
from when they are available, and what to use in older
versions (always show newer and better examples too
by the side of older ones)
- Only use OOP features where you would like to
present them, use simple functions in other areas,
examples need to be clear and simple, but should
show the possibilities and usage of the function[s]
used
I may some up with more suggestions in the future, these
are the ones came to my mind reading your draft. Feel
free to discuss, and incorporate where appropriate.
Goba
Re: [PHP-DOC] coding standards - draft
Hi, On Fri, 28 Dec 2001 18:36:22 +0100 Gabor Hojtsy [EMAIL PROTECTED] wrote: concatenation makes code unreadable I disagree on that. I think strinc concatenation makes the code more readble, because of the face, that what a variable is is clearly separated from what the string is. echo bar is $bar; vs. echo 'bar is '.$bar; additionaly in the first version $bar will be automagically transformed into a string, which is not nessecary. I vote for $array['index'].'string' for arrays. Jan -- Q: Thank Jan? A: http://geschenke.an.dasmoped.net/
Re: [PHP-DOC] coding standards - draft
concatenation makes code unreadable I disagree on that. I think strinc concatenation makes the code more readble, because of the face, that what a variable is is clearly separated from what the string is. echo bar is $bar; vs. echo 'bar is '.$bar; additionaly in the first version $bar will be automagically transformed into a string, which is not nessecary. In the second version, you used the . operator, which also automagically transforms $bar into a string for that operation, there is no difference between the two in this aspect, echo needs string[s] to print out. :) We'll see what others think... Goba
Re: [PHP-DOC] coding standards - draft
Hi, On Fri, 28 Dec 2001 19:03:56 +0100 Gabor Hojtsy [EMAIL PROTECTED] wrote: concatenation makes code unreadable I disagree on that. I think strinc concatenation makes the code more readble, because of the face, that what a variable is is clearly separated from what the string is. echo bar is $bar; vs. echo 'bar is '.$bar; I hope my readbility opinion remains vaild ;) Jan -- Q: Thank Jan? A: http://geschenke.an.dasmoped.net/
Re: [PHP-DOC] coding standards - draft
echo bar is $bar;
vs.
echo 'bar is '.$bar;
additionaly in the first version $bar will be automagically transformed
into a string, which is not nessecary.
In the second version, you used the . operator, which also
automagically transforms $bar into a string for that operation,
there is no difference between the two in this aspect, echo
needs string[s] to print out. :) We'll see what others think...
+1 for not worrying about strings this way, either is okay. If I were to
pick one (which is imho a bad idea) it be using . But, this is not
always the case, depends. Now, I believe the bulk of Jan's comment was
regarding arrays here, which was:
'string '. $arr['key'] .' blah';
And I believe Goba desires:
string {$arr['key']} blah
And I'm more or less for:
string $arr[key] blah
As it's most readable. But the only problem is outside of strings this
creates E_NOTICE as constant 'key' is looked for first and not found, this
may confuse some who don't read the foo[bar] part in manual :) But, {}
syntax here is php4 specific although not a major deal. *shrugs*
Regards,
Philip Olson
Re: [PHP-DOC] coding standards - draft
concatenation makes code unreadable I disagree on that. I think strinc concatenation makes the code more readble, because of the face, that what a variable is is clearly separated from what the string is. echo bar is $bar; vs. echo 'bar is '.$bar; I hope my readbility opinion remains vaild ;) Not for me sorry ;) I prefer the vars inside strings. Goba
Re: [PHP-DOC] coding standards - draft
+1 for not worrying about strings this way, either is okay. If I were to
pick one (which is imho a bad idea) it be using . But, this is not
always the case, depends. Now, I believe the bulk of Jan's comment was
regarding arrays here, which was:
'string '. $arr['key'] .' blah';
And I believe Goba desires:
string {$arr['key']} blah
I talked about ${} and not {$}. ${} also works, at
least in some cases. And it is in the docs. Is this
an inconsistency in PHP?
Goba
[PHP-DOC] cvs: phpdoc /en/language types.xml
gobaFri Dec 28 13:46:53 2001 EDT
Modified files:
/phpdoc/en/language types.xml
Log:
Eliminate all link stuff from CDATA sections, and moved DEV comments
out of example code. The manual pages with these examples were a huge
mess...
Index: phpdoc/en/language/types.xml
diff -u phpdoc/en/language/types.xml:1.69 phpdoc/en/language/types.xml:1.70
--- phpdoc/en/language/types.xml:1.69 Wed Dec 12 17:08:28 2001
+++ phpdoc/en/language/types.xmlFri Dec 28 13:46:53 2001
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.69 $ --
+!-- $Revision: 1.70 $ --
chapter id=language.types
titleTypes/title
@@ -172,12 +172,13 @@
informalexample
programlisting role=php
![CDATA[
-if ($action == show_version) { // == is an link
linkend=language.operatorsoperator/link which returns a typeboolean/type
+// == is an operator which returns a boolean
+if ($action == show_version) {
echo The version is 1.23;
}
// this is not necessary:
-if ($show_separators == true) {
+if ($show_separators == TRUE) {
echo hr\n;
}
@@ -833,20 +834,22 @@
programlisting role=php
![CDATA[
$fruits = array( 'strawberry' = 'red' , 'banana' = 'yellow' );
-echo A banana is $fruits[banana].; // note that this works differently
-outside string-quotes. See link
-linkend=language.types.array.foo-barliteral$foo[bar]/literal outside
strings/link
+
+// note that this works differently outside string-quotes.
+echo A banana is $fruits[banana].;
+
echo This square is $square-width meters broad.;
-echo This square is $square-width00 centimeters broad.; // won't work,
- // for a solution, see the link
linkend=language.types.string.parsing.complexcomplex syntax/link.
+// Won't work. For a solution, see the complex syntax.
+echo This square is $square-width00 centimeters broad.;
+
+]]
!-- XXX this won't work:
echo This square is $square-{width}00 centimeters broad.;
// XXX: php developers: it would be consequent to make this work.
// XXX: like the $obj-{expr} syntax outside a string works,
// XXX: analogously to the ${expr} syntax for variable var's.
--
-]]
/programlisting
/informalexample
simpara
@@ -876,19 +879,21 @@
echo This is {$great}; // works, outputs: This is fantastic
echo This square is {$square-width}00 centimeters broad.;
echo This works: {$arr[4][3]};
-echo This is wrong: {$arr[foo][3]}; // for the same reason
- // as link linkend=language.types.array.foo-bar$foo[bar]/link
-is wrong outside a string.
+
+// This is wrong for the same reason
+// as $foo[bar] is wrong outside a string.
+echo This is wrong: {$arr[foo][3]};
+
echo You should do it this way: {$arr['foo'][3]};
echo You can even write {$obj-values[3]-name};
echo This is the value of the var named $name: {${$name}};
-!-- xxx maybe it's better to leave this out??
+]]
+!-- maybe it's better to leave this out??
// this works, but i disencourage its use, since this is NOT
// involving functions, rather than mere variables, arrays and objects.
$beer = 'Heineken';
echo I'd like to have another {${ strrev('reeb') }}, hips;
- /xxx --
-]]
+ --
/programlisting
/informalexample
/sect4
@@ -911,10 +916,10 @@
example
titleSome string examples/title
programlisting role=php
-![CDATA[
!-- TODO: either move these examples to a example section,
as with arrays, or distribute them under the applicable
sections. --
+![CDATA[
?php
/* Assigning a string. */
$str = This is a string;
@@ -1365,6 +1370,9 @@
, 0= 12 // the value 10 will be overwritten by 12
);
+// empty array
+$empty = array();
+]]
!-- TODO example of
- mixed keys
- overwriting keys
@@ -1372,10 +1380,6 @@
- using vars/functions as key/values
- mixed skipping
--
-
-// empty array
-$empty = array();
-]]
/programlisting
/example
@@ -1412,14 +1416,15 @@
example id=language.types.array.examples.changeloop
titleCollection/title
programlisting role=php
-link linkend=control-structures.foreachforeach/link ( $colors as $key = $color
) {
+![CDATA[
+foreach ($colors as $key = $color) {
// won't work:
-//$color = link linkend=function.strtoupperstrtoupper/link($color);
+//$color = strtoupper($color);
//works:
-$colors[$key] = link linkend=function.strtoupperstrtoupper/link($color);
+$colors[$key] = strtoupper($color);
}
-link linkend=function.print-rprint_r/link($colors);
+print_r($colors);
/* output:
Array
@@ -1430,6 +1435,7 @@
[3] = YELLOW
)
*/
+]]
/programlisting
/example
/para
@@ -1438,8 +1444,9 @@
example
titleOne-based index/title
programlisting role=php
+![CDATA[
$firstquarter = array(1 = 'January', 'February', 'March');
-link linkend=function.print-rprint_r/link($firstquarter);
+print_r($firstquarter);
/* output:
Array
@@
Re: [PHP-DOC] coding standards - draft
3. Keep in mimd: In ![CDATA[... ]] section nothing is parsed. So be sure to put XML-code that needs parsing outside of CDATA sections, e.g. comments or links. See (for example): Language reference|Types|Arrays under Examples; or Language reference|Types|Strings I hope I have now corrected those ugly things in CDATA sections, just committed. Goba
[PHP-DOC] Bug #14742: Example is wrong
From: [EMAIL PROTECTED] Operating system: don\'t care PHP version: 4.1.1 PHP Bug Type: Documentation problem Bug description: Example is wrong http://download.php.net/manual/en/function.strftime.php This is a mistake. print (strftime (%A, in French )); setlocale (LC_TIME, fr_CA); fr is the French language CA is a country, Canada in this case. So, fr_CA is likely Quebec Time or Eastern Time. This example should be replaced with: print (strftime (%A, in French )); setlocale (LC_TIME, fr_FR); Denis -- Edit bug report at: http://bugs.php.net/?id=14742edit=1
Re: [PHP-DOC] Which configure option in which PHP?
Just one question: How do I know, which option is available in PHP 3 and which in PHP 4? download php3 - configure --help same with php4 and compare/diff it If you collect all informations about configuring extensions features, it would be usefull to know under which OS you can use an extension. Georg
Re: [PHP-DOC] coding standards - draft
I talked about ${} and not {$}. ${} also works, at
least in some cases. And it is in the docs. Is this
an inconsistency in PHP?
Regarding inconsistency, I've never used ${} for this and don't see any
docs that mention this syntax for arrays in strings. The docs do mention
{$} syntax though. *shrugs* Not sure what to think :)
${} does not work for 3d arrays, {$} does. Both work for 2d.
You wrote:
- use ${varname} for complex vars in strings, $varname[x]
will confuse readers, as this is illegal outside strings,
concatenation makes code unreadable
I think you meant ${varname['x']} and if so, let's use {$varname['x']}
syntax instead. But then again, I prefer $varname[x] in strings, as
stated earlier. But, the confuse factor does exist so I vote .4 for
both methods and .2 for concatenation ;)
Regards,
Philip Olson
Re: [PHP-DOC] Which configure option in which PHP?
download php3 - configure --help same with php4 and compare/diff it Argh... If you collect all informations about configuring extensions features, it would be usefull to know under which OS you can use an extension. That is one problem. I just can figure out, what's in ./configure --help on Linux. Mark
Re: [PHP-DOC] coding standards - draft
I talked about ${} and not {$}. ${} also works, at
least in some cases. And it is in the docs. Is this
an inconsistency in PHP?
Regarding inconsistency, I've never used ${} for this and don't see any
docs that mention this syntax for arrays in strings. The docs do mention
{$} syntax though. *shrugs* Not sure what to think :)
${} does not work for 3d arrays, {$} does. Both work for 2d.
Why there are two ${} and {$}
See
http://www.php.net/manual/en/language.types.string.php#language.types.string
.parsing
for the examples.
Simple syntax
echo He drunk some ${beer}s; // works
Complex Syntax
echo You can even write {$obj-values[3]-name};
Don't know why there is a simple syntax for that... ${} if there
is a {$}. This is just to confuse people, like me... There are
some things explained there about ${} problems with more
complex expressions. The docs says, this is why {$} exists...
Huh...
Goba
Re: [PHP-DOC] coding standards - draft
This makes sense as $beers is not a set variable. {$beer}s works too
though, seems okay that both work. Anyway, this isn't an array ;-))
OK, can you give an example you can do with ${} but you can't with
{$} and the opposite? Would be nice to clear at least my mind about
that :) We may include an example in the manual to show people
why we have two frighteningly similar things for the same thing
echo this is ${bar};
echo this is {$bar};
Goba
Re: [PHP-DOC] Documenting configure options/Updating andsplittinginstall.configure.php
Some related thoughts: a) Explain different options: --with, --enable, --disable b) Example configure lines. c) A Configuration faq: /faq/configuration.xml d) How does Windows fit into all of this? Have a Windows section. How/where does one get dlls? e) How do RPM and deb users add extensions? Ex. php-pgsql Also, why would one want php-devel package? Mention apache-devel too. f) Separate php3/php4 information so php4 users don't have to read about php3 and vice versa. Not sure what Seperate means here, either by section or a simple two column table or something. Seems repetitive but then again, not a major deal. g) If applicatable, refer to config.xml. Or, include config.xml information outright. See Below. The main reason I write is share a vision for a new config.xml which includes a marriage between the current ini_set() and config.xml docs. The vision includes the following information: a) Name b) Value Type: Boolean, string, or integer c) Description d) Notes: default hist, see also, related info... e) Version it came into existence (maybe include as note) f) Default Value: as per php.ini-dist g) Changeable: PHP_INI_ . USER|PERDIR|SYSTEM|ALL There are some issues with this. For example, register_globals is PHP_INI_ALL when in the real world it's impossible to set as PHP_INI_USER. Sure the local value gets set but it's of no consequence. This should be evaluated. Here's an example (don't pay attention to look|feel|specifics yet): register_globals (boolean) d: 0PERDIR|SYSTEMv: 2.0 Tells whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables. ... Note: Default value was 1 before 4.2.0 That's just an example :) Some thoughts: 1) Too much information. Most directives have been around since php3, why always include (e)? Not sure if simply including (e) as a note is better or not. 2) How to layout all this information yet remain pretty. 3) Be sure to keep default values up-to-date and note the changes. 4) As mentioned earlier, PHP_INI_ALL isn't always real. Reference links: http://www.php.net/manual/en/function.ini-set.php http://www.php.net/manual/en/configuration.php (config.xml) http://lxr.php.net/source/php4/main/main.c#206 (g) All thoughts welcome :) Regards, Philip Olson
Re: [PHP-DOC] coding standards - draft
This makes sense as $beers is not a set variable. {$beer}s works too
though, seems okay that both work. Anyway, this isn't an array ;-))
OK, can you give an example you can do with ${} but you can't with
{$} and the opposite? Would be nice to clear at least my mind about
that :) We may include an example in the manual to show people
why we have two frighteningly similar things for the same thing
echo this is ${bar};
echo this is {$bar};
Hmm :) Variable variables come to mind but then again ${$var} can be seen
as a mix of both :)
The simple/complex separation seems to show people what you can and cannot
do with {braces}. That's what comes to mind at least. *shrugs* It all
seems complex. Through the coming days I'll give it more thought :)
Regards,
Philip Olson
Re: [PHP-DOC] cvs: phpdoc /en/chapters install.xml
Modified files: /phpdoc/en/chapters install.xml Log: Total update of the install.configure.php part with all configure options of PHP 4.1.0 I hope this is okay. It's just the beginning. If something is wrong, blame me ;) Mark
Re: [PHP-DOC] Documenting configure options/Updating and splittinginstall.configure.php
a) Explain different options: --with, --enable, --disable Later ;) b) Example configure lines. Later ;) c) A Configuration faq: /faq/configuration.xml Great idea! There are always lots of problems during an installation. d) How does Windows fit into all of this? Have a Windows section. How/where does one get dlls? There is a Windows section with a bit of help to dlls at http://www.php.net/manual/en/install.windows.php e) How do RPM and deb users add extensions? Ex. php-pgsql Also, why would one want php-devel package? Mention apache-devel too. Would be nice too. f) Separate php3/php4 information so php4 users don't have to read about php3 and vice versa. Not sure what Seperate means here, either by section or a simple two column table or something. Seems repetitive but then again, not a major deal. There will come information (again) which options is for PHP 3 and which is for PHP 4. Mark
Re: [PHP-DOC] cvs: phpdoc /en/chapters install.xml
I hope this is okay. It's just the beginning. If something is wrong, blame me ;) it's okay as long as you run 'make test' first, *hint* *hint* ;) Regards, Philip Olson
[PHP-DOC] cvs: phpdoc /en/chapters install.xml
mk Fri Dec 28 17:29:12 2001 EDT Modified files: /phpdoc/en/chapters install.xml Log: Typo Index: phpdoc/en/chapters/install.xml diff -u phpdoc/en/chapters/install.xml:1.97 phpdoc/en/chapters/install.xml:1.98 --- phpdoc/en/chapters/install.xml:1.97 Fri Dec 28 16:57:05 2001 +++ phpdoc/en/chapters/install.xml Fri Dec 28 17:29:12 2001 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.97 $ -- +!-- $Revision: 1.98 $ -- chapter id=installation titleInstallation/title @@ -821,7 +821,7 @@ /term listitem para - Not information yet. + No information yet. /para /listitem /varlistentry
[PHP-DOC] cvs: phpdoc /kr Translators
fuzzy74 Fri Dec 28 17:34:46 2001 EDT Added files: /phpdoc/kr Translators Log: cvs add Translators in kr .
Re: [PHP-DOC] coding standards - draft
OK, can you give an example you can do with ${} but you can't with
{$} and the opposite? Would be nice to clear at least my mind about
that :) We may include an example in the manual to show people
why we have two frighteningly similar things for the same thing
echo this is ${bar};
echo this is {$bar};
Hmm :) Variable variables come to mind but then again ${$var} can be seen
as a mix of both :)
That is something indicates, why both works, and should work, and
why ${varname[1]} should not. But it works as you reported... Hm...
Goba
Re: [PHP-DOC] Documenting configure options/Updating andsplittinginstall.configure.php
Some related thoughts: Well thought out suggestions :) Hope this is not just a nice dream vision :)) Goba
Re: [PHP-DOC] Documenting configure options/Updating andsplittinginstall.configure.php
Well thought out suggestions :) Hope this is not just a nice dream vision :)) I hope so too. But, since my daughter (her 2nd birthday was today ;) went to bed earlier as usual, i was able to hack down the options. I really hope, that someone will help me/Jan to document that stuff better. But I think, I did the start, now its up to all the other documentators (and me too), Mark
[PHP-DOC] cvs: phpdoc / TODO
mk Fri Dec 28 19:49:21 2001 EDT Modified files: /phpdoc TODO Log: Added configure options (started by mk and jan) Index: phpdoc/TODO diff -u phpdoc/TODO:1.8 phpdoc/TODO:1.9 --- phpdoc/TODO:1.8 Sun Dec 16 11:08:08 2001 +++ phpdoc/TODO Fri Dec 28 19:49:21 2001 @@ -37,6 +37,7 @@ nesting level. - Remark in shmop.xml whether or not the old shm_* funcnames still work in the current version of PHP. (search for the TODO mark) + - Document configure options in install.xml (mk, jan) (from php4/TODO): - update curl documentation
[PHP-DOC] cvs: phpdoc / TODO
philip Fri Dec 28 22:13:37 2001 EDT Modified files: /phpdoc TODO Log: Removed done items, added two for philip (config.xml and include/require docs). Index: phpdoc/TODO diff -u phpdoc/TODO:1.9 phpdoc/TODO:1.10 --- phpdoc/TODO:1.9 Fri Dec 28 19:49:21 2001 +++ phpdoc/TODO Fri Dec 28 22:13:36 2001 @@ -25,25 +25,18 @@ disabled in safe-mode.' - Note which functions don't work with win32. - Mark binary (un)safe functions - - Add the ob-tip to all functions that output there results and have -no straight-forward way of getting there contents in a string - (var_dump, highlight-string) (jeroen) - Add example to the tip.ob-capture; tip (preferable a link to a example) - Bug the dev's to rename functions like hw_getobjectbyquerycollobj - - Document somewhere that you can also use php in shell-scripts? - - print_r will NOT continue forever anymore on recursive arr's. - - var_dump also not, but vardump simply quits at a too-high -nesting level. - Remark in shmop.xml whether or not the old shm_* funcnames still work in the current version of PHP. (search for the TODO mark) - Document configure options in install.xml (mk, jan) + - Expand config.xml documentation (philip) + - Update include/require _once docs (philip) (from php4/TODO): - update curl documentation - - write documentation for the bzip2 extension - write documentation for the zziplib extension (from bugs): - - see bugs.php.net for now - + - see bugs.php.net for now \ No newline at end of file
[PHP-DOC] cvs: phpdoc /en/chapters install.xml
mk Fri Dec 28 22:42:07 2001 EDT Modified files: /phpdoc/en/chapters install.xml Log: Another one... Good night! Index: phpdoc/en/chapters/install.xml diff -u phpdoc/en/chapters/install.xml:1.99 phpdoc/en/chapters/install.xml:1.100 --- phpdoc/en/chapters/install.xml:1.99 Fri Dec 28 22:36:47 2001 +++ phpdoc/en/chapters/install.xml Fri Dec 28 22:42:07 2001 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.99 $ -- +!-- $Revision: 1.100 $ -- chapter id=installation titleInstallation/title @@ -1037,7 +1037,7 @@ /para /listitem /varlistentry - varlistentry id=install.configure.with-zlib-dir=lt;DIRgt; + varlistentry id=install.configure.with-zlib-dir term parameter--with-zlib-dir=lt;DIRgt;/parameter /term @@ -1208,7 +1208,7 @@ /para /listitem /varlistentry - varlistentry id=install.configure.enable-dba=shared + varlistentry id=install.configure.enable-dba term parameter--enable-dba=shared/parameter /term
[PHP-DOC] cvs: phpdoc /fr language-snippets.ent
eschmid Sat Dec 29 01:02:37 2001 EDT Modified files: /phpdoc/fr language-snippets.ent Log: Needed by crack.xml. Index: phpdoc/fr/language-snippets.ent diff -u phpdoc/fr/language-snippets.ent:1.14 phpdoc/fr/language-snippets.ent:1.15 --- phpdoc/fr/language-snippets.ent:1.14Mon Nov 12 00:02:03 2001 +++ phpdoc/fr/language-snippets.ent Sat Dec 29 01:02:37 2001 @@ -1,6 +1,11 @@ -!-- PHPDoc snippets $Id: language-snippets.ent,v 1.14 2001/11/12 05:02:03 dams Exp $ -- +!-- PHPDoc snippets $Id: language-snippets.ent,v 1.15 2001/12/29 06:02:37 eschmid +Exp $ -- !ENTITY warn.experimental 'warningsimparaCe module est emphasisEXPERIMENTAL/emphasis. Cela signifie que le comportement de ces fonctions, leurs noms et concregrave;tement, TOUT ce qui est documenteacute; ici peut changer dans un futur proche, SANS PREAVIS! Soyez-en conscient, et utiliser ce module agrave; vos risques et peacute;rils./simpara/warning' !ENTITY warn.experimental.func 'warningsimparaCette fonction est emphasisEXPERIMENTALE/emphasis. Cela signifie que le comportement de cette fonction, son nom et concregrave;tement, TOUT ce qui est documenteacute; ici peut changer dans un futur proche, SANS PREAVIS! Soyez-en conscient, et utilisez cette fonction agrave; vos risques et peacute;rils./simpara/warning' + +!ENTITY warn.undocumented.func 'warningsimparaThis function is +currently not documented, only the argument list is +available./simpara/warning' + !ENTITY tip.ob-capture 'tipsimparaComme toutes les fonctions affichent directement des reacute;sultats au navigateur, vous pouvez utiliser link linkend=ref.outcontrolles fonctions de gestion des sorties/link pour capturer le contenu de cette fonction et le sauver, par exemple, dans une chaicirc;ne./simpara/tip' !ENTITY return.success 'Retourne true; en cas de succegrave;s, false; en cas d#39;eacute;chec.' !ENTITY return.falseproblem'warningsimparaCette fonction peut retourner false;, mais elle peut aussi retourner une valeur eacute;quivalent agrave; false;, utilisable dans une condition if simple. Utilisez l#39;link linkend=language.operators.comparisonopeacute;rateur ===/link pour tester la valeur exacte de cette fonction.simpara/warning'
[PHP-DOC] cvs: phpdoc /fr/appendices history.xml
eschmid Sat Dec 29 01:09:11 2001 EDT Modified files: /phpdoc/fr/appendices history.xml Log: It is not so good to have incomplete chapters here. Index: phpdoc/fr/appendices/history.xml diff -u phpdoc/fr/appendices/history.xml:1.4 phpdoc/fr/appendices/history.xml:1.5 --- phpdoc/fr/appendices/history.xml:1.4Mon Nov 12 00:17:51 2001 +++ phpdoc/fr/appendices/history.xmlSat Dec 29 01:09:11 2001 @@ -1 +1 @@ -?xml version=1.0 encoding=iso-8859-1?!-- $Revision: 1.4 $ --!-- This is a first draft, currently, nobody is working on it--chaptPHP's historysectOverview of PHP's development \ No newline at end of file +?xml version=1.0 encoding=iso-8859-1?!-- $Revision: 1.5 $ --!-- This is a +first draft, currently, nobody is working on itchaptPHP's historysectOverview of +PHP's development-- \ No newline at end of file
[PHP-DOC] cvs: phpdoc /fr preface.xml
eschmid Sat Dec 29 01:21:52 2001 EDT Modified files: /phpdoc/fr preface.xml Log: ID about is now defined in en/appendices/about.xml. Index: phpdoc/fr/preface.xml diff -u phpdoc/fr/preface.xml:1.16 phpdoc/fr/preface.xml:1.17 --- phpdoc/fr/preface.xml:1.16 Wed Dec 12 15:48:39 2001 +++ phpdoc/fr/preface.xml Sat Dec 29 01:21:52 2001 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.16 $ -- +!-- $Revision: 1.17 $ -- preface id=preface titlePreacute;face/title abstract @@ -19,7 +19,7 @@ permet agrave; PHP de faire des scripts utilisant des interfaces X. /simpara /abstract - sect1 id=about + sect1 id=see.en.appendices.about.xml titleA propos de ce manuel/title para Ce manuel est eacute;crit en acronymXML/acronym avec ulink
[PHP-DOC] cvs: phpdoc /cs language-snippets.ent
eschmid Sat Dec 29 01:42:46 2001 EDT Modified files: /phpdoc/cs language-snippets.ent Log: Added missing entities. Index: phpdoc/cs/language-snippets.ent diff -u phpdoc/cs/language-snippets.ent:1.6 phpdoc/cs/language-snippets.ent:1.7 --- phpdoc/cs/language-snippets.ent:1.6 Mon Dec 3 16:12:01 2001 +++ phpdoc/cs/language-snippets.ent Sat Dec 29 01:42:46 2001 @@ -1,10 +1,14 @@ -!-- PHPDoc snippets $Id: language-snippets.ent,v 1.6 2001/12/03 21:12:01 luk Exp $ -- +!-- PHPDoc snippets $Id: language-snippets.ent,v 1.7 2001/12/29 06:42:46 eschmid Exp +$ -- !ENTITY warn.experimental 'warningsimparaTento modul je emphasisEXPERIMENTÁLNÍ/emphasis. To znamená, ¾e chování tìchto funkcí a jejich názvy, pøesnìji øeèeno COKOLI, co je zde zdokumentováno, se v budoucích verzích PHP mù¾e BEZ OHLÁ©ENÍ zmìnit. Berte to v úvahu a pou¾ívejte tento modul na vlastní nebezpeèí./simpara/warning' !ENTITY warn.experimental.func 'warningsimparaTato funkce je emphasisEXPERIMENTÁLNÍ/emphasis. To znamená, ¾e chování této funkce a její název, pøesnìji øeèeno COKOLI, co je zde zdokumentováno, se v budoucích verzích PHP mù¾e BEZ OHLÁ©ENÍ zmìnit. Berte to v úvahu a pou¾ívejte tuto funkci na vlastní nebezpeèí./simpara/warning' +!ENTITY warn.undocumented.func 'warningsimparaThis function is +currently not documented, only the argument list is +available./simpara/warning' + !ENTITY tip.ob-capture 'tipsimparaJako pro cokoliv, co posílá své výsledky pøímo do prohlí¾eèe, mù¾ete pou¾ít link linkend=ref.outcontrolfunkce pro øízení výstupu/link k zachycení výstupu této funkce a jeho ulo¾ení - napøíklad - do øetìzce (typestring/type)./simpara/tip' !ENTITY return.success 'Vrací constantTRUE/constant pøi úspìchu, constantFALSE/constant pøi selhání.' @@ -14,6 +18,10 @@ !ENTITY note.bin-safe 'notesimparaTato funkce je binárnì bezpeèná./simpara/note' !ENTITY note.no-windows 'notesimparaTato funkce není implementována na platformách Windows./simpara/note' + +!ENTITY note.func-callback 'notesimparaInstead of a function name, an +array containing an object reference and a method name can also be +supplied./simpara/note' !-- Notes for safe-mode limited functions: -- !ENTITY note.sm.disabled 'notesimparasm.disabled;/simpara/note'
[PHP-DOC] cvs: phpdoc /cs preface.xml
eschmid Sat Dec 29 01:54:02 2001 EDT Modified files: /phpdoc/cs preface.xml Log: cs/preface.xml is not uptodate. The remaining non SGML characters could be ignored. Index: phpdoc/cs/preface.xml diff -u phpdoc/cs/preface.xml:1.6 phpdoc/cs/preface.xml:1.7 --- phpdoc/cs/preface.xml:1.6 Wed Dec 12 15:45:54 2001 +++ phpdoc/cs/preface.xml Sat Dec 29 01:54:02 2001 @@ -13,7 +13,7 @@ /simpara /abstract - sect1 id=about + sect1 id=see.en.chapters.about.xml titleAbout this Manual/title para Tento manuál je napsán v acronymXML/acronym s pou¾itím ulink
[PHP-DOC] cvs: phpdoc /es language-snippets.ent preface.xml /es/appendices history.xml
eschmid Sat Dec 29 02:08:43 2001 EDT Modified files: /phpdoc/es language-snippets.ent preface.xml /phpdoc/es/appendices history.xml Log: Fixed some errors. Index: phpdoc/es/language-snippets.ent diff -u phpdoc/es/language-snippets.ent:1.5 phpdoc/es/language-snippets.ent:1.6 --- phpdoc/es/language-snippets.ent:1.5 Thu Jul 12 09:39:53 2001 +++ phpdoc/es/language-snippets.ent Sat Dec 29 02:08:43 2001 @@ -1,9 +1,13 @@ -!-- PHPDoc snippets $Id: language-snippets.ent,v 1.5 2001/07/12 13:39:53 jeroen Exp $ -- +!-- PHPDoc snippets $Id: language-snippets.ent,v 1.6 2001/12/29 07:08:43 eschmid Exp +$ -- !ENTITY warn.experimental 'warningsimparaThis module is emphasisEXPERIMENTAL/emphasis. That means, that the behaviour of these functions, these function names, in concreto ANYTHING documented here can change in a future release of PHP WITHOUT NOTICE. Be warned, and use this module at your own risk./simpara/warning' !ENTITY warn.experimental.func 'warningsimparaThis function is emphasisEXPERIMENTAL/emphasis. That means, that the behaviour of this function, this function name, in concreto ANYTHING documented here can change in a future release of PHP WITHOUT NOTICE. Be warned, and use this function at your own risk./simpara/warning' + +!ENTITY warn.undocumented.func 'warningsimparaThis function is +currently not documented, only the argument list is +available./simpara/warning' !ENTITY tip.ob-capture 'tipsimparaAs with anything that outputs its result directly to the browser, you can use the link linkend=ref.outcontroloutput-control functions/link to capture the output of this function, and save it - for example - in a typestring/type./simpara/tip' Index: phpdoc/es/preface.xml diff -u phpdoc/es/preface.xml:1.8 phpdoc/es/preface.xml:1.9 --- phpdoc/es/preface.xml:1.8 Wed Dec 12 15:47:45 2001 +++ phpdoc/es/preface.xml Sat Dec 29 02:08:43 2001 @@ -12,7 +12,7 @@ /simpara /abstract - sect1 id=about + sect1 id=see.en.appendices.about.xml titleSobre este Manual/title para Este manual está escrito en acronymSGML/acronym usando ulink Index: phpdoc/es/appendices/history.xml diff -u phpdoc/es/appendices/history.xml:1.2 phpdoc/es/appendices/history.xml:1.3 --- phpdoc/es/appendices/history.xml:1.2Wed Nov 14 17:27:03 2001 +++ phpdoc/es/appendices/history.xmlSat Dec 29 02:08:43 2001 @@ -1,4 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? +!-- chaptHistoria de PHP sectUna mirada al desarrollo de PHP - +--
[PHP-DOC] cvs: phpdoc /kr language-snippets.ent preface.xml /kr/appendices history.xml
eschmid Sat Dec 29 02:35:20 2001 EDT Modified files: /phpdoc/kr language-snippets.ent preface.xml /phpdoc/kr/appendices history.xml Log: Fixed some errors. Index: phpdoc/kr/language-snippets.ent diff -u phpdoc/kr/language-snippets.ent:1.5 phpdoc/kr/language-snippets.ent:1.6 --- phpdoc/kr/language-snippets.ent:1.5 Thu Jul 12 09:39:54 2001 +++ phpdoc/kr/language-snippets.ent Sat Dec 29 02:35:20 2001 @@ -1,9 +1,13 @@ -!-- PHPDoc snippets $Id: language-snippets.ent,v 1.5 2001/07/12 13:39:54 jeroen Exp $ -- +!-- PHPDoc snippets $Id: language-snippets.ent,v 1.6 2001/12/29 07:35:20 eschmid Exp +$ -- !ENTITY warn.experimental 'warningsimparaThis module is emphasisEXPERIMENTAL/emphasis. That means, that the behaviour of these functions, these function names, in concreto ANYTHING documented here can change in a future release of PHP WITHOUT NOTICE. Be warned, and use this module at your own risk./simpara/warning' !ENTITY warn.experimental.func 'warningsimparaThis function is emphasisEXPERIMENTAL/emphasis. That means, that the behaviour of this function, this function name, in concreto ANYTHING documented here can change in a future release of PHP WITHOUT NOTICE. Be warned, and use this function at your own risk./simpara/warning' + +!ENTITY warn.undocumented.func 'warningsimparaThis function is +currently not documented, only the argument list is +available./simpara/warning' !ENTITY tip.ob-capture 'tipsimparaAs with anything that outputs its result directly to the browser, you can use the link linkend=ref.outcontroloutput-control functions/link to capture the output of this function, and save it - for example - in a typestring/type./simpara/tip' Index: phpdoc/kr/preface.xml diff -u phpdoc/kr/preface.xml:1.5 phpdoc/kr/preface.xml:1.6 --- phpdoc/kr/preface.xml:1.5 Wed Dec 12 15:54:10 2001 +++ phpdoc/kr/preface.xml Sat Dec 29 02:35:20 2001 @@ -8,7 +8,7 @@ 이 언어의 목적은 웹개발자들이 동적인 웹문서를 빠르고 쉽게 작성할 수 있도록 하는 것이다. /simpara /abstract - sect1 id=about + sect1 id=see.en.appendices.about.xml title이 매뉴얼에 대하여/title para 이 매뉴얼은 ulink url=url.docbook.xml;DocBook XML DTD/ulink를 사용한 acronymXML/acronym로 되어있고, Index: phpdoc/kr/appendices/history.xml diff -u phpdoc/kr/appendices/history.xml:1.5 phpdoc/kr/appendices/history.xml:1.6 --- phpdoc/kr/appendices/history.xml:1.5Wed Nov 14 18:14:07 2001 +++ phpdoc/kr/appendices/history.xmlSat Dec 29 02:35:20 2001 @@ -1,4 +1,5 @@ ?xml version=1.0 encoding=utf-8? +!-- chaptPHP의 역사 sectPHP 개발의 총람(Overview) - +--
[PHP-DOC] cvs: phpdoc /nl language-snippets.ent preface.xml /nl/appendices history.xml
eschmid Sat Dec 29 02:47:29 2001 EDT Modified files: /phpdoc/nl language-snippets.ent preface.xml /phpdoc/nl/appendices history.xml Log: Fixed some errors. Index: phpdoc/nl/language-snippets.ent diff -u phpdoc/nl/language-snippets.ent:1.6 phpdoc/nl/language-snippets.ent:1.7 --- phpdoc/nl/language-snippets.ent:1.6 Thu Jul 12 09:39:54 2001 +++ phpdoc/nl/language-snippets.ent Sat Dec 29 02:47:28 2001 @@ -1,19 +1,37 @@ -!-- PHPDoc snippets $Id: language-snippets.ent,v 1.6 2001/07/12 13:39:54 jeroen Exp $ -- +!-- PHPDoc snippets $Id: language-snippets.ent,v 1.7 2001/12/29 07:47:28 eschmid Exp +$ -- !ENTITY warn.experimental 'warningsimparaDeze module is emphasisEXPERIMENTEEL/emphasis. Dat betekent, dat het gedrag van deze functies, deze functienamen, in concreto ALLES dat hier gedocumenteerd is in een toekomstige uitgave van PHP ZONDER WAARSCHUWING kan veranderen. Wees gewaarschuwd, en gebruik deze module op eigen risico./simpara/warning' !ENTITY warn.experimental.func 'warningsimparaDeze functie is emphasisEXPERIMENTEEL/emphasis. Dat betekent, dat het gedrag van deze functie, deze functienaam, in concreto ALLES dat hier gedocumenteerd is in een toekomstige uitgave van PHP ZONDER WAARSCHUWING kan veranderen. Wees gewaarschuwd, en gebruik deze functie op eigen risico./simpara/warning' +!ENTITY warn.undocumented.func 'warningsimparaThis function is +currently not documented, only the argument list is +available./simpara/warning' + !ENTITY tip.ob-capture 'tipsimparaAs with anything that outputs its result directly to the browser, you can use the link linkend=ref.outcontroloutput-control functions/link to capture the output of this function, and save it - for example - in a typestring/type./simpara/tip' +!ENTITY tip.fopen-wrapper 'tipsimparaYou can use a URL as a +filename with this function if the fopen wrappers have been enabled. +See functionfopen/function for more details./simpara/tip' + !ENTITY return.success 'Geeft true; terug bij succes, false; indien er een fout is opgetreden.' +!ENTITY return.falseproblem 'warningsimparaThis function may +return false;, but may also return a value evaluating to false; in a +simple if statement. Please use link +linkend=language.operators.comparisonthe === operator/link for +testing the return value of this function./simpara/warning' + !ENTITY note.not-bin-safe 'warningsimparaThis function is not (yet) binary safe!/simpara/warning' !ENTITY note.bin-safe 'notesimparaThis function is binary-safe/simpara/note' !ENTITY note.no-windows 'notesimparaThis function is not implemented on Windows-platforms/simpara/note' + +!ENTITY note.func-callback 'notesimparaInstead of a function name, an +array containing an object reference and a method name can also be +supplied./simpara/note' !-- Notes for safe-mode limited functions: -- !ENTITY note.sm.disabled 'notesimparasm.disabled;/simpara/note' Index: phpdoc/nl/preface.xml diff -u phpdoc/nl/preface.xml:1.8 phpdoc/nl/preface.xml:1.9 --- phpdoc/nl/preface.xml:1.8 Wed Dec 12 15:55:39 2001 +++ phpdoc/nl/preface.xml Sat Dec 29 02:47:28 2001 @@ -14,7 +14,7 @@ /simpara /abstract - sect1 id=about + sect1 id=see.en.appendices.about.xml titleOver deze handleiding/title para Deze handleiding is geschreven in acronymXML/acronym, gebruik Index: phpdoc/nl/appendices/history.xml diff -u phpdoc/nl/appendices/history.xml:1.3 phpdoc/nl/appendices/history.xml:1.4 --- phpdoc/nl/appendices/history.xml:1.3Wed Nov 14 17:36:37 2001 +++ phpdoc/nl/appendices/history.xmlSat Dec 29 02:47:28 2001 @@ -1,4 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? +!-- chaptPHP's geschiedenis sectOverzicht van de geschiedenis van PHP - +--
