[PHP-DOC] I'm back and things have changed!
Well, after a long hiatus, I'm trying to get back involved in the phpdoc community again. After a quick cvs checkout, it seems a lot of the phpdoc tree has changed. =) Anything I should know before I start contributing again? Daniel
Re: [PHP-DOC] howto
I'm sorry, but I never meant it to be silly. I only responded as to why the howto wasn't part of the appendix. Or were you talking specifically to Jim Winstead? Daniel - Original Message - From: Egon Schmid [EMAIL PROTECTED] To: Daniel Beckham [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, September 28, 2001 5:56 PM Subject: Re: [PHP-DOC] howto Please stop such useless and silly postings on the php-doc list. -Egon - Original Message - From: Daniel Beckham [EMAIL PROTECTED] To: phpdoc [EMAIL PROTECTED] Sent: Friday, September 28, 2001 10:50 PM Subject: Re: [PHP-DOC] howto Because it has nothing to do with PHP itself.. only writing PHP documentation. It's completely useless to the regular PHP user. Daniel - Original Message - From: Jim Winstead [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 28, 2001 3:29 PM Subject: [PHP-DOC] howto why isn't this just an appendix to the rest of the documentation? jim
Re: [PHP-DOC] howto
Because it has nothing to do with PHP itself.. only writing PHP documentation. It's completely useless to the regular PHP user. Daniel - Original Message - From: Jim Winstead [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 28, 2001 3:29 PM Subject: [PHP-DOC] howto why isn't this just an appendix to the rest of the documentation? jim
[PHP-DOC] cvs: phpdoc /en/functions pcntl.xml
danbeck Fri Sep 28 17:40:05 2001 EDT
Modified files:
/phpdoc/en/functionspcntl.xml
Log:
completed intro text, added a couple of function examples
Index: phpdoc/en/functions/pcntl.xml
diff -u phpdoc/en/functions/pcntl.xml:1.3 phpdoc/en/functions/pcntl.xml:1.4
--- phpdoc/en/functions/pcntl.xml:1.3 Fri Sep 21 18:47:45 2001
+++ phpdoc/en/functions/pcntl.xml Fri Sep 28 17:40:05 2001
@@ -1,10 +1,26 @@
?xml encoding=iso-8859-1?
-!-- $Revision: 1.3 $ --
+!-- $Revision: 1.4 $ --
reference id=ref.pcntl
titleProcess Control Functions/title
titleabbrevPCNTL/titleabbrev
partintro
para
+Process Control support in PHP implements the Unix style of
+process creation, program execution, signal handling and process
+termination. Process Control should not be enabled within a
+webserver environment and unexpected results may happen if any
+Process Control functions are used within a webserver environment.
+ /para
+ para
+This documentation is intended to explain the general usage of
+each of the Process Control functions. For detailed information
+about Unix process control you are encouraged to consult your
+systems documentation including fork(2), waitpid(2) and signal(2)
+or a comprehensive reference such as citationAdvanced
+Programming in the UNIX Environment by W. Richard Stevens
+(Addison-Wesley)/citation.
+ /para
+ para
Process Control support in PHP is not enabled by default. You
will need to use the link
linkend=install.configure.enable-pcntl--enable-pcntl/link
@@ -89,7 +105,6 @@
/table
/para
-
sect1 id=pcntl-example
titleProcess Control Example/title
para
@@ -176,6 +191,23 @@
parent's context, no child process will be created, and a PHP
error is raised.
/para
+ example
+titlefunctionpcntl_fork/function Example/title
+programlisting role=php
+lt;?php
+
+$pid = pcntl_fork();
+if ($pid == -1) {
+ die(could not fork);
+} else if ($pid) {
+ // we are the parent
+} else {
+ // we are the child
+}
+
+?gt;
+/programlisting
+ /example
para
See also functionpcntl_waitpid/function and
functionpcntl_signal/function.
@@ -210,6 +242,35 @@
functionpcntl_signal/function returns true; on success or
false; on failure.
/para
+ example
+titlefunctionpcntl_fork/function Example/title
+programlisting role=php
+lt;?php
+
+// setup signal handlers
+pcntl_signal(SIGTERM, sig_handler);
+pcntl_signal(SIGHUP, sig_handler);
+
+// signal handler function
+function sig_handler($signo) {
+
+ switch($signo) {
+ case SIGTERM:
+ // handle shutdown tasks
+ exit;
+ break;
+ case SIGHUP:
+ // handle restart tasks
+ break;
+ default:
+ // handle all other signals
+ }
+
+}
+
+?gt;
+/programlisting
+ /example
para
See also functionpcntl_fork/function and
functionpcntl_waitpid/function.
[PHP-DOC] cvs: phpdoc /en/functions pcntl.xml
danbeck Fri Sep 21 17:07:38 2001 EDT Modified files: /phpdoc/en/functionspcntl.xml Log: added missing waitpid macro functions code examples are still missing and intro text needs more information Index: phpdoc/en/functions/pcntl.xml diff -u phpdoc/en/functions/pcntl.xml:1.1 phpdoc/en/functions/pcntl.xml:1.2 --- phpdoc/en/functions/pcntl.xml:1.1 Fri Sep 14 16:57:26 2001 +++ phpdoc/en/functions/pcntl.xml Fri Sep 21 17:07:38 2001 @@ -1,5 +1,5 @@ ?xml encoding=iso-8859-1? -!-- $Revision: 1.1 $ -- +!-- $Revision: 1.2 $ -- reference id=ref.pcntl titleProcess Control Functions/title titleabbrevPCNTL/titleabbrev @@ -182,7 +182,41 @@ /para /refsect1 /refentry - + + + refentry id=function.pcntl-signal + refnamediv + refnamepcntl_signal/refname + refpurposeInstalls a signal handler/refpurpose + /refnamediv + refsect1 + titleDescription/title + funcsynopsis +funcprototype + funcdefbool functionpcntl_signal/function/funcdef + paramdefint parametersigno/parameter/paramdef + paramdefmixed parameterhandle/parameter/paramdef +/funcprototype + /funcsynopsis + para +The functionpcntl_signal/function function installs a new +signal handler for the signal indicated by +parametersigno/parameter. The signal handler is set to +parameterhandler/parameter which may be the name of a user +created function, or either of the two global constants SIG_IGN +or SIG_DFL. + /para + para +functionpcntl_signal/function returns true; on success or +false; on failure. + /para + para +See also functionpcntl_fork/function and +functionpcntl_waitpid/function. + /para + /refsect1 + /refentry + refentry id=function.pcntl-waitpid refnamediv @@ -218,44 +252,41 @@ /para para The value of parameterpid/parameter can be one of the following: -variablelist - varlistentry - termlt; -1/term - listitem - simpara - wait for any child process whose process group ID is equal to - the absolute value of parameterpid/parameter. - /simpara - /listitem - /varlistentry - varlistentry - term-1/term - listitem - simpara - wait for any child process; this is the same behaviour that - the wait function exhibits. - /simpara - /listitem - /varlistentry - varlistentry - term0/term - listitem - simpara - wait for any child process whose process group ID is equal to - that of the calling process. - /simpara - /listitem - /varlistentry - varlistentry - termgt; 0/term - listitem - simpara - wait for the child whose process ID is equal to the value of - parameterpid/parameter. - /simpara - /listitem - /varlistentry -/variablelist +table + titlepossible values for parameterpid/parameter/title + tgroup cols=2 + tbody + row + entryliterallt; -1/literal/entry + entry +wait for any child process whose process group ID is equal to +the absolute value of parameterpid/parameter. + /entry + /row + row + entryliteral-1/literal/entry + entry +wait for any child process; this is the same behaviour that +the wait function exhibits. + /entry + /row + row +entryliteral0/literal/entry +entry +wait for any child process whose process group ID is equal to +that of the calling process. +/entry + /row + row +entryliteralgt; 0/literal/entry +entry +wait for the child whose process ID is equal to the value of +parameterpid/parameter. +/entry + /row + /tbody + /tgroup +/table /para para functionpcntl_waitpid/function will store status information @@ -271,26 +302,27 @@ para The value of parameteroptions/parameter is the value of zero or more of the following two global constants -literalOR/literaled together: -variablelist - varlistentry - termWNOHANG/term - listitem - simpara - return immediately if no child has exited. - /simpara - /listitem - /varlistentry - varlistentry - termWUNTRACED/term - listitem - simpara - return for children which are stopped, and whose status has - not been reported. - /simpara - /listitem - /varlistentry -/variablelist +literalOR/literal'ed together: +table + titlepossible values for parameteroptions/parameter/title + tgroup cols=2 + tbody + row +entryliteralWNOHANG/literal/entry +entry +return immediately if no child has exited. + /entry + /row + row +entryliteralWUNTRACED/literal/entry +entry +return for children which are stopped, and whose status has +
Re: [PHP-DOC] cvs: phpdoc /howto README
Guys, I've been away from the list for a week or two and I've pretty much missed this conversation. Just an FYI to throw in here, the howto wasn't quite finished and hadn't yet been tested on any machines but my own. Take that for what you will. =) Daniel - Original Message - From: Egon Schmid [EMAIL PROTECTED] To: Hojtsy Gabor [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, September 08, 2001 2:37 PM Subject: Re: [PHP-DOC] cvs: phpdoc /howto README Hojtsy Gabor wrote: I have noticed that: [...] OK, things worked well, till this line :) eschmid@marliesle:/usr/local/usr/phpdoc make howto make: *** Warning: File `howto/howto.xml' has modification time in the future (2001-09-08 20:43:58 2001-09-08 20:41:33) Hm, your date setting seems to be broken. I don't know how the modification dates are stored in CVS. If they are stored as on the commiting clients computer, than my date settings are broken :)) I don't know. My date setting is not broken. The date settings are stored on both sides and are synced with an update. /usr/bin/openjade -wno-idref -i lang-en -c /usr/share/sgml/CATALOG.docbk30 -d howto.dsl -V use-output-dir -t sgml ./phpdocxml.dcl ./howto/howto.xml /usr/bin/openjade:./html-common.dsl:12:7:E: identifier toc-depth already defined in same part /usr/bin/openjade:howto.dsl:28:1: first definition was here This error is printed on my screen two, but it just won't stop to build the howto html files, they are generated. This seems to be a warning, that toc levels are defined twice. The DSL file is made by Daniel Backem, and I have not modified it, it worked the same in the upper directory, with its own makefile. You mean Daniel Beckham? The modification time is a warning and the already defined toc-depth identifier is an error. make: warning: Clock skew detected. Your build may be incomplete. This may be because of the date conflicts mentioned above. No I am sure and I have tested it with Debian and SuSE on different maschines. eschmid@marliesle:/usr/local/usr/phpdoc Please test it before you commit it or ask an editor :) I have tested. Worked. And generated these HTML files with autoconf ./configure make howto I get this error, but the files are generated. | $ make howto | ../phpdoc-tools/jade/jade.exe -wno-idref -i lang-en -c ../phpdoc-tools/jade/catalog | -c ../phpdoc-tools/iso-entities/cata | log -c ../phpdoc-tools/dsssl/docbook/catalog -d howto.dsl -V use-output-dir -t | sgml ./phpdocxml.dcl ./howto/howto.xml | e:\phpcvs\phpdoc-tools\jade\jade.exe:./html-common.dsl:12:7:E: identifier | toc-depth already defined in same part | e:\phpcvs\phpdoc-tools\jade\jade.exe:howto.dsl:28:1: first definition was here I am using cygwin so this is why I can use Unix/Linux tools on Windows :))) If you don't see the time conflict, it is probably on your client side or the Gates Company gots something wrong. I have a Windows ME system here too, but I use it almost to watch TV. -Egon
Re: [PHP-DOC] cvs: phpdoc /howto README
Damn... no need for hostilities. =) Daniel - Original Message - From: Hojtsy Gabor [EMAIL PROTECTED] To: Egon Schmid [EMAIL PROTECTED] Cc: Daniel Beckham [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, September 14, 2001 10:17 AM Subject: Re: [PHP-DOC] cvs: phpdoc /howto README The question is answerd. Look close to this error message: identifier toc-depth already defined in same part. So a identifier is defined before reading html-common.dsl before line number 12. The question was: ARE THE HTML FILES GENERATED? ARE THE HTML FILES GENERATED? ARE THE HTML FILES GENERATED? ARE THE HTML FILES GENERATED? ARE THE HTML FILES GENERATED? ARE THE HTML FILES GENERATED? ARE THE HTML FILES GENERATED? Goba
[PHP-DOC] cvs: phpdoc /en/chapters install.xml
danbeck Fri Sep 14 16:54:14 2001 EDT Modified files: /phpdoc/en/chapters install.xml Log: added configure option for pcntl support Index: phpdoc/en/chapters/install.xml diff -u phpdoc/en/chapters/install.xml:1.76 phpdoc/en/chapters/install.xml:1.77 --- phpdoc/en/chapters/install.xml:1.76 Sun Aug 19 07:04:19 2001 +++ phpdoc/en/chapters/install.xml Fri Sep 14 16:54:13 2001 @@ -1,5 +1,5 @@ ?xml encoding=iso-8859-1? -!-- $Revision: 1.76 $ -- +!-- $Revision: 1.77 $ -- chapter id=installation titleInstallation/title @@ -1564,6 +1564,20 @@ /para /listitem /varlistentry + varlistentry id=install.configure.enable-pcntl + term + parameter--enable-pcntl/parameter + /term + listitem + para + PHP 3: Option not available in PHP 3 + /para + para + PHP 4: Enable process control functions. (fork, waitpid, + signal, et. al.) + /para + /listitem + /varlistentry varlistentry id=install.configure.disable-rpath term parameter--disable-rpath/parameter
[PHP-DOC] cvs: phpdoc /en/functions pcntl.xml
danbeck Fri Sep 14 16:57:26 2001 EDT
Added files:
/phpdoc/en/functionspcntl.xml
Log:
initial draft of process control functions... several
functions are still not documented, intro is not
completed and several examples are missing.
This file has not yet been added to manual.xml.in.
Index: phpdoc/en/functions/pcntl.xml
+++ phpdoc/en/functions/pcntl.xml
?xml encoding=iso-8859-1?
!-- $Revision: 1.1 $ --
reference id=ref.pcntl
titleProcess Control Functions/title
titleabbrevPCNTL/titleabbrev
partintro
para
Process Control support in PHP is not enabled by default. You
will need to use the link
linkend=install.configure.enable-pcntl--enable-pcntl/link
configuration option when compiling PHP to enable Process Control
support.
/para
para
The following list of signals are supported by the Process Control
functions. Please see your systems signal(7) man page for details
of the default behavior of these signals.
table
titleSupported Signals/title
tgroup cols=2
tbody
row
entryliteralSIG_IGN/literal/entry
entryliteralSIGFPE/literal/entry
entryliteralSIGCONT/literal/entry
/row
row
entryliteralSIG_DFL/literal/entry
entryliteralSIGKILL/literal/entry
entryliteralSIGSTOP/literal/entry
/row
row
entryliteralSIG_ERR/literal/entry
entryliteralSIGUSR1/literal/entry
entryliteralSIGTSTP/literal/entry
/row
row
entryliteralSIGHUP/literal/entry
entryliteralSIGUSR2/literal/entry
entryliteralSIGTTIN/literal/entry
/row
row
entryliteralSIGINT/literal/entry
entryliteralSIGSEGV/literal/entry
entryliteralSIGTTOU/literal/entry
/row
row
entryliteralSIGQUIT/literal/entry
entryliteralSIGPIPE/literal/entry
entryliteralSIGURG/literal/entry
/row
row
entryliteralSIGILL/literal/entry
entryliteralSIGALRM/literal/entry
entryliteralSIGXCPU/literal/entry
/row
row
entryliteralSIGTRAP/literal/entry
entryliteralSIGTERM/literal/entry
entryliteralSIGXFSZ/literal/entry
/row
row
entryliteralSIGABRT/literal/entry
entryliteralSIGSTKFLT/literal/entry
entryliteralSIGVTALRM/literal/entry
/row
row
entryliteralSIGIOT/literal/entry
entryliteralSIGCHLD/literal/entry
entryliteralSIGPROF/literal/entry
/row
row
entryliteralSIGBUS/literal/entry
entryliteralSIGCLD/literal/entry
entryliteralSIGWINCH/literal/entry
/row
row
entryliteralSIGPOLL/literal/entry
entryliteralSIGIO/literal/entry
entryliteralSIGPWR/literal/entry
/row
row
entryliteralSIGSYS/literal/entry
entryliteral/literal/entry
entryliteral/literal/entry
/row
/tbody
/tgroup
/table
/para
sect1 id=pcntl-example
titleProcess Control Example/title
para
This example forks off a daemon process with a signal handler.
/para
example
titleProcess Control Example/title
programlisting role=php
lt;?php
$pid = pcntl_fork();
if ($pid == -1) {
die(could not fork);
} else if ($pid) {
exit(); // we are the parent
} else {
// we are the child
}
// detatch from the controlling terminal
if (!posix_setsid()) {
die(could not detach from terminal);
}
// setup signal handlers
pcntl_signal(SIGTERM, sig_handler);
pcntl_signal(SIGHUP, sig_handler);
// loop forever performing tasks
while(1) {
// do something interesting here
}
function sig_handler($signo) {
switch($signo) {
case SIGTERM:
// handle shutdown tasks
exit;
break;
case SIGHUP:
// handle restart tasks
break;
default:
// handle all other signals
}
}
?
/programlisting
/example
/sect1
/partintro
refentry id=function.pcntl-fork
refnamediv
refnamepcntl_fork/refname
refpurposeForks the currently running process/refpurpose
/refnamediv
refsect1
titleDescription/title
funcsynopsis
funcprototype
funcdefint functionpcntl_fork/function/funcdef
void/
/funcprototype
/funcsynopsis
para
The functionpcntl_fork/function function creates a child
process that differs from the parent process only in it's PID and
PPID. Please see your system's fork(2) man page for specific details as to
how fork works on your system.
/para
para
On success, the PID of the child process is returned in the
parent's thread of execution, and a 0 is returned in the child's
thread of execution. On failure, a -1 will be returned in the
parent's context, no child process will be created, and a PHP
error is raised.
/para
para
See also functionpcntl_waitpid/function and
[PHP-DOC] cvs: phpdoc /en/features file-upload.xml
danbeck Wed Jul 18 17:35:30 2001 EDT Modified files: /phpdoc/en/features file-upload.xml Log: added double quotes around method for consistency Index: phpdoc/en/features/file-upload.xml diff -u phpdoc/en/features/file-upload.xml:1.19 phpdoc/en/features/file-upload.xml:1.20 --- phpdoc/en/features/file-upload.xml:1.19 Tue Jul 10 17:12:59 2001 +++ phpdoc/en/features/file-upload.xml Wed Jul 18 17:35:30 2001 @@ -25,7 +25,7 @@ example titleFile Upload Form/title programlisting -lt;FORM ENCTYPE=quot;multipart/form-dataquot; ACTION=quot;_URL_quot; METHOD=POSTgt; +lt;FORM ENCTYPE=quot;multipart/form-dataquot; ACTION=quot;_URL_quot; +METHOD=quot;POSTquot;gt; lt;INPUT TYPE=quot;hiddenquot; name=quot;MAX_FILE_SIZEquot; value=quot;1000quot;gt; Send this file: lt;INPUT NAME=quot;userfilequot; TYPE=quot;filequot;gt; lt;INPUT TYPE=quot;submitquot; VALUE=quot;Send Filequot;gt;
Re: [PHP-DOC] Setting up PHP documentation for building
It might be looking for the php4 sources. In the parent directory of the phpdoc tree, checkout the php4 tree also... then try running configure again. BTW, emacs is just the best phpdoc editor out there, IMHO. You may consider just working directly on that debian box. =) Daniel - Original Message - From: Damien Seguy [EMAIL PROTECTED] To: phpdoc [EMAIL PROTECTED] Sent: Wednesday, July 11, 2001 5:43 AM Subject: [PHP-DOC] Setting up PHP documentation for building Hi all, I'm trying to set up some linux box to build the PHP documentation (hehe, I see Egon's eyes widening...). This is debian 2.2.18, and Jade and docbook are already Installed. I cvs'ed all en tree, and also all files in phpdoc (configure.in, bightml.in). autoconf works (at least, it doesn't say anything, and write some files), but ./configure tells me that it can't find any sources in . and .. What am I missing? Best regards, Damien Seguy
Re: [PHP-DOC] cvs: phpdoc /en/functions ircg.xml
This entity isn't valid. I think you forgot to commit global.ent also? Daniel - Original Message - From: Damien Seguy [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 11, 2001 7:18 AM Subject: [PHP-DOC] cvs: phpdoc /en/functions ircg.xml dams Wed Jul 11 08:18:34 2001 EDT Modified files: /phpdoc/en/functions ircg.xml Log: Adding a link to home page Index: phpdoc/en/functions/ircg.xml diff -u phpdoc/en/functions/ircg.xml:1.3 phpdoc/en/functions/ircg.xml:1.4 --- phpdoc/en/functions/ircg.xml:1.3 Sun Jul 8 08:24:00 2001 +++ phpdoc/en/functions/ircg.xml Wed Jul 11 08:18:34 2001 @@ -5,6 +5,9 @@ para Internet Relay Chat Gateway ... /para + para + Based on ulink url=url.ircg;IRCG/ulink, from Sascha Schumann. + /para /partintro refentry id=function.ircg-pconnect
Re: [PHP-DOC] Setting up PHP documentation for building
Title: RE: [PHP-DOC] Setting up PHP documentation for building Ouch.. ok.. sorry. =) I use it to generate the function lists and summaries... my configure looks for it and finds it.. but you are probably right. Daniel - Original Message - From: Hojtsy Gábor To: 'Daniel Beckham' ; 'Damien Seguy' Cc: 'phpdoc' Sent: Wednesday, July 11, 2001 9:20 AM Subject: RE: [PHP-DOC] Setting up PHP documentation for building It might be looking for the php4 sources. In the parent directory of the phpdoc tree, checkout the php4 tree also... then try running configure again. BTW, emacs is just the best phpdoc editor out there, IMHO. You may consider just working directly on that debian box. =) No, no. You do not need the php4 source tree to build the manuals. It is not true... :)) Goba
[PHP-DOC] Use `make test' Was: Re: [PHP-DOC] cvs: phpdoc /en/faq general.xml
Yes.. please do. I've been guilty of it in the past and I see errors fairly often. Everyone please remember... always do a `make test` before committing anything to the phpdoc tree. If you do commit incorrectly written xml to the tree, the manual will not be generated that evening and other contributors changes will not show up. I'm not just singling out Damien (as I said, I've been guilty too). Everyone please remember this. Thank you, Daniel Beckham - Original Message - From: Hojtsy Gabor [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 10, 2001 5:07 AM Subject: [PHP-DOC] cvs: phpdoc /en/faq general.xml goba Tue Jul 10 06:07:56 2001 EDT Modified files: /phpdoc/en/faq general.xml Log: XML errors corrected, OK, the english manual will build now with the new FAQ section. It will show up tomorow morning online :) Please always do make test before committing such new things :) Index: phpdoc/en/faq/general.xml diff -u phpdoc/en/faq/general.xml:1.4 phpdoc/en/faq/general.xml:1.5 --- phpdoc/en/faq/general.xml:1.4 Tue Jul 10 05:58:47 2001 +++ phpdoc/en/faq/general.xml Tue Jul 10 06:07:56 2001 @@ -4,34 +4,35 @@ partintro para -This section holds the most general questions about PHP : +This section holds the most general questions about PHP: what it is and what it does. /para /partintro refentry id=faq.general.what refnamediv -refnameWhat is PHP ?/refname -refpurposeWhat is PHP ?/refpurpose +refnameWhat is PHP?/refname +refpurposeWhat is PHP?/refpurpose /refnamediv refsect1 titleDescription/title para - From the ulink url=faqurl.php.manual;manual/ulink : -para + From the ulink url=faqurl.php.manual;manual/ulink: /para +para PHP is an HTML-embedded scripting language. Much of its syntax is borrowed from C, Java and Perl with a couple of unique PHP-specific features thrown in. The goal of the language is to allow web developers to write dynamically generated pages quickly. -para /para -A nice introduction to PHP by Stig Sæther Bakken can be found -ulink url=faqurl.zend.introduction;here/ulink on the Zend -website. +para + A nice introduction to PHP by Stig Saelig;ther Bakken can be found + ulink url=faqurl.zend.introduction;here/ulink on the Zend + website. /para /refsect1 /refentry + refentry id=faq.general.relation-between-versions refnamediv refnameWhat is the relation between the versions?/refname @@ -42,23 +43,26 @@ para PHP/FI 2.0 is an early and no longer supported version of PHP. PHP 3 is the successor to PHP/FI 2.0 and is a lot nicer. PHP 4 is the latest - generation of PHP, which uses the ulink url=faqurl.zend;Zend engine/ulink - under the hood. + generation of PHP, which uses the ulink url=faqurl.zend;Zend + engine/ulink under the hood. /para /refsect1 /refentry + refentry id=faq.general.running-concurent-versions refnamediv +refnameCan I run several versions of PHP at the same time?/refname refpurposeCan I run several versions of PHP at the same time?/refpurpose /refnamediv refsect1 titleDescription/title para - Yes. See the filenameINSTALL/filename file that is included in the PHP 4 - source distribution. + Yes. See the filenameINSTALL/filename file that is included + in the PHP 4 source distribution. /para /refsect1 /refentry + refentry id=faq.general.differences-php3-php4 refnamediv refnameWhat are the differences between PHP 3 and PHP 4?/refname @@ -67,37 +71,39 @@ refsect1 titleDescription/title para -There are ulink url=faqurl.zend.articles;a couple of articles/ulink -written on this by the authors of PHP4. Here's a -list of some of the more important new features: -itemizedlist - listitem - simparaExtended API module./simpara - /listitem - listitem - simparaGeneralized build process under UNIX/simpara - /listitem - listitem - simparaGeneric web server interface that also supports multi-threaded web servers/simpara - /listitem - listitem - simparaImproved syntax highlighter/simpara - /listitem - listitem - simparaNative HTTP session support/simpara - /listitem - listitem - simparaOutput buffering support/simpara - /listitem - listitem - simparaMore powerful configuration system/simpara - /listitem - listitem - simparaReference counting/simpara - /listitem -/itemizedlist -Please see the ulink url=faqurl.zend.new;What's new in PHP4 overview/ulink -for a detailed explanation of these features and more. + There are ulink url=faqurl.zend.articles;a couple of articles/ulink + written on this by the authors of PHP4. Here's a list of some
Re: [PHP-DOC] faqfiles [refentry is not so good]
Yes, that was part of my reasoning before.. also, the refentry blocks need a lot of extraneous tags and such that aren't necessary for a faq. i.e. Damien had to put a refname tag in his refnamediv block so that he would conform to the DTD, but it's just duplicated information. Daniel - Original Message - From: Hojtsy Gabor [EMAIL PROTECTED] To: PHP-Doc list [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, July 10, 2001 5:32 AM Subject: [PHP-DOC] faqfiles [refentry is not so good] Hi Damien and the others! I have just built the new manual with the FAQ section... I was curious :) But the results are not really good... Maybe refentry is not the best wat to store the faq. It would be better to generate fewer but longer pages... I am not saying I would like to see the FAQ on one page (it is not soo friendly now), but now this is too splinterd. Goba
Re: [PHP-DOC] faqfiles [refentry is not so good]
Damien, you may consider getting openjade and docbook setup on your system. It's not very hard at all and you can do all sorts of testing and such with the phpdoc tree. Daniel - Original Message - From: Hojtsy Gabor [EMAIL PROTECTED] To: Damien Seguy [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: PHP-Doc list [EMAIL PROTECTED] Sent: Tuesday, July 10, 2001 6:41 AM Subject: Re: [PHP-DOC] faqfiles [refentry is not so good] as far as I know DocBook supports QA sections, see: http://www.oreilly.com/catalog/docbook/chapter/book/qandaset.html That is too easy : you read the docs =D OK, this sound MUCH better to me. Here is an updated version. Goba : can you test this on your Jade? Ehm. Erhm. You should read the docs more carefully. qandaset is not allowed in refentry context Errors: general.xml:12:11:E: document type does not allow element qandaset here end tag for reference which is not finished Please try again :) Goba
Re: [PHP-DOC] cvs: phpdoc /en/faq general.xml
This breaks `make test'. Will this affect automatic manual generation at php.net/manual/? Daniel - Original Message - From: Damien Seguy [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 09, 2001 8:52 AM Subject: [PHP-DOC] cvs: phpdoc /en/faq general.xml dams Mon Jul 9 09:52:59 2001 EDT Added files: /phpdoc/en/faq general.xml Log: Adding first draft for FAQ Index: phpdoc/en/faq/general.xml +++ phpdoc/en/faq/general.xml reference id=faq.general titleGeneral Information/title titleabbrevGeneral Information about PHP/titleabbrev partintro para This section holds the most general questions about PHP : what it is and what it does. /para /partintro refentry id=faq.general.what refnamediv refpurposeWhat is PHP ?/refpurpose /refnamediv refsect1 titleDescription/title para From the ulink url=url.php.manual;manual/ulink : para /para PHP is an HTML-embedded scripting language. Much of its syntax is borrowed from C, Java and Perl with a couple of unique PHP-specific features thrown in. The goal of the language is to allow web developers to write dynamically generated pages quickly. para /para A nice introduction to PHP by Stig Sæther Bakken can be found ulink url=url.zend.introduction;here/ulink on the Zend website. /para /refsect1 /refentry refentry id=faq.general.relation-between-versions refnamediv refpurposeWhat is the relation between the versions?/refpurpose /refnamediv refsect1 titleDescription/title para PHP/FI 2.0 is an early and no longer supported version of PHP. PHP 3 is the successor to PHP/FI 2.0 and is a lot nicer. PHP 4 is the latest generation of PHP, which uses the ulink url=url.zend;Zend engine/ulink under the hood. /para /refsect1 /refentry refentry id=faq.general.running-concurent-versions refnamediv refpurposeCan I run several versions of PHP at the same time ?/refpurpose /refnamediv refsect1 titleDescription/title para Yes. See the filenameINSTALL/filename file that is included in the PHP 4 source distribution. /para /refsect1 /refentry refentry id=faq.general.differences-php3-php4 refnamediv refpurposeWhat are the differences between PHP 3 and PHP 4?/refpurpose /refnamediv refsect1 titleDescription/title para There are ulink url=url.zend.articles;a couple of articles/ulink written on this by the authors of PHP4. Here's a list of some of the more important new features: itemizedlist listitem simparaExtended API module./simpara /listitem listitem simparaGeneralized build process under UNIX/simpara /listitem listitem simparaGeneric web server interface that also supports multi-threaded web servers/simpara /listitem listitem simparaImproved syntax highlighter/simpara /listitem listitem simparaNative HTTP session support/simpara /listitem listitem simparaOutput buffering support/simpara /listitem listitem simparaMore powerful configuration system/simpara /listitem listitem simparaReference counting/simpara /listitem /itemizedlist Please see the ulink url=url.zend.new;What's new in PHP4 overview/ulink for a detailed explanation of these features and more. /para /refsect1 /refentry /reference
[PHP-DOC] cvs: phpdoc /en/faq general.xml
danbeck Mon Jul 9 17:14:27 2001 EDT Modified files: /phpdoc/en/faq general.xml Log: added emacs sgml block at end Index: phpdoc/en/faq/general.xml diff -u phpdoc/en/faq/general.xml:1.1 phpdoc/en/faq/general.xml:1.2 --- phpdoc/en/faq/general.xml:1.1 Mon Jul 9 09:52:59 2001 +++ phpdoc/en/faq/general.xml Mon Jul 9 17:14:27 2001 @@ -98,4 +98,21 @@ /para /refsect1 /refentry - /reference \ No newline at end of file + /reference + + !-- Keep this comment at the end of the file + Local variables: + mode: sgml + sgml-omittag:t + sgml-shorttag:t + sgml-minimize-attributes:nil + sgml-always-quote-attributes:t + sgml-indent-step:1 + sgml-indent-data:t + sgml-parent-document:nil + sgml-default-dtd-file:../../manual.ced + sgml-exposed-tags:nil + sgml-local-catalogs:nil + sgml-local-ecat-files:nil + End: + --
Re: [PHP-DOC] Re: [PHP-NOTES] note 13852 added to function.mail.php
I don't think it's appropriate to have a specific PHP function to send MIME email. Especially since no special code or function needs to be written that isn't already available from the standard PHP function library. But, some thing like this is an excellent candidate for a PEAR class.. as a matter of fact, this is what PEAR was meant to be used for. Daniel - Original Message - From: Jeroen van Wolffelaar [EMAIL PROTECTED] To: Zak Greant [EMAIL PROTECTED] Cc: Daniel Beckham [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; PHP Developers Mailing List [EMAIL PROTECTED] Sent: Saturday, July 07, 2001 7:58 AM Subject: Re: [PHP-DOC] Re: [PHP-NOTES] note 13852 added to function.mail.php The mail() function can be used to send email with attachments and special types of content. This is accomplished via MIME-encoding - for more information, see http://www.zend.com/zend/spotlight/sendmimeemailpart1.php; Just a wild idea, but maybe we should add a real PHP-function which can send MIME-mail? It's really something that would be useful in PHP... Has anyone idea's for a good syntax? --zak Jeroen
Re: [PHP-DOC] Re: [PHP-NOTES] note 13852 added to function.mail.php
I don't think that would really help unless the MIME functions had detailed instructions. The problem is that these sort of folks are pretty new to CGI scripting and the Internet in general and don't understand that isn't just not even remotely appropriate to ask questions about foo in a forum devoted to bar. In fact, it's fscking rude. But, enough ranting. =) What MIME-encoded mail functions are you talking about? Do you mean external tutorials and examples? Daniel - Original Message - From: Zak Greant [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: phpdoc [EMAIL PROTECTED] Sent: Friday, July 06, 2001 2:13 AM Subject: [PHP-DOC] Re: [PHP-NOTES] note 13852 added to function.mail.php Notes asking this question are becoming like a rash. It seems that I have deleted about one a day for the last few days... Perhaps we should add a note in the docs on where to find MIME-encoded mail functions? --zak - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 06, 2001 12:53 AM Subject: [PHP-NOTES] note 13852 added to function.mail.php HI, Can anyone help me in sending email as HTML format and which is containing some 'GIFs' in it. Thanks, Raj http://www.php.net/manual/en/function.mail.php -- PHP Notes Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DOC] RFC reserved.xml :
I think it would be useful to have them in a multi-column table layout to start with. Whether they are grouped by some means or not, it's a toss up. Some people have mentioned in the errata that NULL, echo, print, exit, die, endif, endforeach. Also, this isn't a keyword, $this is the special variable. Daniel - Original Message - From: Damien Seguy [EMAIL PROTECTED] To: Daniel Beckham [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, July 06, 2001 4:03 AM Subject: [PHP-DOC] RFC reserved.xml : on 6/07/01 3:48, Daniel Beckham at [EMAIL PROTECTED] wrote: Hi, The list of reserverd words itself is quite bogus by the way... It really should be reviewed soon. I did this first draft. The goal was to gather all special words from PHP, besides function names. I ordered them alphabetically. This is basically the whole point. I'll be happy to share any other opinions. Best regards, Damien Seguy
[PHP-DOC] Manual toc not updated for some reason
I'm not sure why, but the either the online manual's toc isn't being updated or something screwy is going on. The appendix list at http://www.php.net/manual/en/ shows the incorrect short description of PHP Resource Types. It's incorrectly displayed as PHP's resource types. It should be PHP Resource Types as it is in cvs. Anyone know why might have happened? Daniel
Re: [PHP-DOC] Re: [PHP-NOTES] note 13852 added to function.mail.php
I think that is a good idea actually. Even better that it's a link to a article on zend.com. Maybe this would be a good note/note? Daniel - Original Message - From: Zak Greant [EMAIL PROTECTED] To: Daniel Beckham [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: phpdoc [EMAIL PROTECTED] Sent: Friday, July 06, 2001 3:43 PM Subject: Re: [PHP-DOC] Re: [PHP-NOTES] note 13852 added to function.mail.php We would just need to state something like the following near the end of the document. The mail() function can be used to send email with attachments and special types of content. This is accomplished via MIME-encoding - for more information, see http://www.zend.com/zend/spotlight/sendmimeemailpart1.php; --zak
Re: [PHP-DOC] Re: phpdoc /it/appendices reserved.xml
I would agree with you. Where do you propose we start? At the least, it could be organized better. Daniel - Original Message - From: Jeroen van Wolffelaar [EMAIL PROTECTED] To: Simone Cortesi [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, July 05, 2001 5:29 PM Subject: [PHP-DOC] Re: phpdoc /it/appendices reserved.xml The list of reserverd words itself is quite bogus by the way... It really should be reviewed soon. jeroen - Original Message - From: Simone Cortesi [EMAIL PROTECTED] Newsgroups: php.doc To: [EMAIL PROTECTED] Sent: Thursday, July 05, 2001 10:55 PM Subject: cvs: phpdoc /it/appendices reserved.xml cortesi Thu Jul 5 16:55:12 2001 EDT Added files: /phpdoc/it/appendices reserved.xml Log: initial import in to CVS and translation Index: phpdoc/it/appendices/reserved.xml +++ phpdoc/it/appendices/reserved.xml appendix id=reserved titleParole riservate nel PHP/title para Questa egrave; la lista delle parole riservate nel PHP e delle solite costanti. itemizedlist listitem simpara link linkend=language.operators.logicaland/link. /simpara /listitem listitem simpara link linkend=control-structures.breakbreak/link. /simpara /listitem listitem simpara link linkend=control-structures.switchcase/link. /simpara /listitem listitem simpara link linkend=keyword.classclass/link. /simpara /listitem listitem simpara link linkend=control-structures.continuecontinue/link. /simpara /listitem listitem simpara link linkend=control-structures.switchdefault/link. /simpara /listitem listitem simpara link linkend=control-structures.do.whiledo/link. /simpara /listitem listitem simpara link linkend=control-structures.elseelse/link. /simpara /listitem listitem simpara link linkend=control-structures.elseifelseif/link. /simpara /listitem listitem simpara functionempty/function. /simpara /listitem listitem simpara link linkend=control-structures.alternative-syntaxendfor/link. /simpara /listitem listitem simpara link linkend=control-structures.alternative-syntaxendif/link. /simpara /listitem listitem simpara link linkend=control-structures.alternative-syntaxendswitch/link. /simpara /listitem listitem simpara link linkend=control-structures.alternative-syntaxendwhile/link. /simpara /listitem listitem simpara link linkend=language.constantsE_ALL/link. /simpara /listitem listitem simpara link linkend=language.constantsE_PARSE/link. /simpara /listitem listitem simpara link linkend=language.constantsE_ERROR/link. /simpara /listitem listitem simpara link linkend=language.constantsE_WARNING/link. /simpara /listitem listitem simpara link linkend=keyword.classextends/link. /simpara /listitem listitem simpara link linkend=language.constantsliteralFALSE/literal/link. /simpara /listitem listitem simpara link linkend=control-structures.forfor/link. /simpara /listitem listitem simpara link linkend=control-structures.foreachforeach/link. /simpara /listitem listitem simpara link linkend=functions.user-definedfunction/link. /simpara /listitem listitem simpara link linkend=control-structures.ifif/link. /simpara /listitem listitem simpara functioninclude/function. /simpara /listitem listitem simpara functioninclude_once/function. /simpara /listitem listitem simpara link linkend=language.variables.scopeglobal/link. /simpara /listitem listitem simpara functionlist/function. /simpara /listitem listitem simpara link linkend=keyword.classnew/link. /simpara /listitem listitem simpara link linkend=language.operators.logicalnot/link. /simpara /listitem listitem simpara link linkend=language.operators.logicalor/link. /simpara /listitem listitem simpara link linkend=keyword.parentparent/link. /simpara /listitem listitem simpara link linkend=language.constantsPHP_OS/link. /simpara /listitem listitem simpara link linkend=language.constantsPHP_VERSION/link. /simpara /listitem listitem simpara functionrequire/function. /simpara /listitem listitem simpara functionrequire_once/function. /simpara /listitem listitem simpara link linkend=functions.user-definedreturn/link. /simpara /listitem listitem simpara
[PHP-DOC] cvs: phpdoc /en/appendices resources.xml
danbeck Tue Jul 3 11:35:14 2001 EDT Modified files: /phpdoc/en/appendices resources.xml Log: grammar, typo and capitilization fixes note: please do not use the pronoun you when writing documentation Index: phpdoc/en/appendices/resources.xml diff -u phpdoc/en/appendices/resources.xml:1.8 phpdoc/en/appendices/resources.xml:1.9 --- phpdoc/en/appendices/resources.xml:1.8 Tue Apr 17 09:51:52 2001 +++ phpdoc/en/appendices/resources.xml Tue Jul 3 11:35:14 2001 @@ -1,19 +1,20 @@ appendix id=resource - titlePHP's resource types/title + titlePHP Resource Types/title para - Here is the function's list which create, use or destroy - PHP resources. You know when a variable is a resource - by using functionis_resource/function, and what resource - type is this variable by using functionget_resource_type/function. + The following is a list of functions which create, use or destroy + PHP resources. The function functionis_resource/function can be + used to determine if a variable is a resource and + functionget_resource_type/function will return the type of + resource it is. table - titleRessource types/title + titleResource Types/title tgroup cols=5 thead row - entryResource type's name/entry - entryCreated by/entry - entryUsed by/entry - entryDestroyed by/entry + entryResource Type Name/entry + entryCreated By/entry + entryUsed By/entry + entryDestroyed By/entry entryDefinition/entry /row /thead @@ -2068,4 +2069,4 @@ /tgroup /table /para -/appendix \ No newline at end of file +/appendix
[PHP-DOC] cvs: phpdoc /en/functions session.xml uodbc.xml
danbeck Tue Jul 3 11:36:36 2001 EDT Modified files: /phpdoc/en/functionssession.xml uodbc.xml Log: correcting make test errors in session and uodbc reformated weird spacing in uodbc Index: phpdoc/en/functions/session.xml diff -u phpdoc/en/functions/session.xml:1.43 phpdoc/en/functions/session.xml:1.44 --- phpdoc/en/functions/session.xml:1.43Tue Jul 3 02:58:35 2001 +++ phpdoc/en/functions/session.xml Tue Jul 3 11:36:35 2001 @@ -564,9 +564,9 @@ expect the connection to still be valid the next time the session is restored. PHP functions that return a resource are identified by having a return type of - literalresource/literal in their function definitions. - You may also find a list of resource-creating fonctions in - the link linkend=resourcesappendices/link. + literalresource/literal in their function definitions. A + list of functions that return resources are available in the + link linkend=resourceresource types/link appendix. /para /note note Index: phpdoc/en/functions/uodbc.xml diff -u phpdoc/en/functions/uodbc.xml:1.19 phpdoc/en/functions/uodbc.xml:1.20 --- phpdoc/en/functions/uodbc.xml:1.19 Thu Jun 28 11:54:29 2001 +++ phpdoc/en/functions/uodbc.xml Tue Jul 3 11:36:35 2001 @@ -506,56 +506,61 @@ array. The array will contain the column values starting at array index 0. /para - para -example - titlefunctionodbc_fetch_into/function pre 4.0.6 example /title - programlisting role=php + para +example + titlefunctionodbc_fetch_into/function pre 4.0.6 example /title + programlisting role=php $rc = odbc_fetch_into($res_id, $my_array); - /programlisting - or - programlisting role=php + /programlisting + para + or + /para + programlisting role=php $rc = odbc_fetch_into($res_id, $row, $my_array); - + $rc = odbc_fetch_into($res_id, 1, $my_array); - /programlisting -/example - /para - para -As of PHP 4.0.5 the parameterresult_array/parameter does not need -to be passed by reference any longer. - /para - para -As of PHP 4.0.6 the parameterrownumber/parameter cannot be passed -as a constant, but rather as a variable. - /para - para -example - titlefunctionodbc_fetch_into/function 4.0.6 example/title - programlisting role=php + /programlisting +/example + /para + para +As of PHP 4.0.5 the parameterresult_array/parameter does not +need to be passed by reference any longer. + /para + para +As of PHP 4.0.6 the parameterrownumber/parameter cannot be +passed as a constant, but rather as a variable. + /para + para +example + titlefunctionodbc_fetch_into/function 4.0.6 example/title + programlisting role=php $rc = odbc_fetch_into($res_id, $my_array); - /programlisting - or - programlisting role=php + /programlisting + para + or + /para + programlisting role=php $row = 1; $rc = odbc_fetch_into($res_id, $row, $my_array); - /programlisting -/example - /para - para -Future: In PHP 4.1, this function will be moved to the following format: - funcsynopsis - funcprototype - funcdefint functionodbc_fetch_into/function/funcdef - paramdefint parameterresult_id/parameter/paramdef - paramdefarray parameterresult_array/parameter/paramdef - paramdefint parameteroptionalrownumber/optional/parameter/paramdef - /funcprototype - /funcsynopsis -Please note, that parameterrownumber/parameter will be optional, -while parameterresult_array/parameter is not. - /para - /refsect1 - /refentry + /programlisting +/example + /para + para +Future: In PHP 4.1, this function will be moved to the following +format: +funcsynopsis + funcprototype + funcdefint functionodbc_fetch_into/function/funcdef + paramdefint parameterresult_id/parameter/paramdef + paramdefarray parameterresult_array/parameter/paramdef + paramdefint parameteroptionalrownumber/optional/parameter/paramdef + /funcprototype +/funcsynopsis +Please note, that parameterrownumber/parameter will be optional, +while parameterresult_array/parameter is not. + /para + /refsect1 + /refentry refentry id=function.odbc-fetch-row refnamediv
[PHP-DOC] Re: Re[2]: PHP Bug ID: 11833
- Original Message - From: Michal Izydorski [EMAIL PROTECTED] To: Daniel Beckham [EMAIL PROTECTED] Sent: Tuesday, July 03, 2001 10:44 AM Subject: Re[2]: PHP Bug ID: 11833 Sorry, the relation behind $HTTP_*_VARS tables and $PHP_SELF, according the manual, is only, that both are predefined variables, but there aren't any words about $PHP_SELF and register_globals connection. The associative arrays are mixed with 'keys' of its elements. It was my problem. I think, that separation of this two variables types will be more clear. Ok, I now see what you are saying. The $PHP_SELF variable is described as a special PHP variable like $HTTP_SERVER_VARS, et. al., but it stops acting like a special variable once register_globals is turned off. This is definitly a documenation issue and I will add a note in the docs about this behavior. Thank you for persisting with your point. =) Second problem is, that I can't set any session variables when I turn register_globals Off. I read documentation carefully, but following code doesn't work - variable user isn't set in main.php. I'm not so sure what's mean of : Please submit this as a session related bug in the PHP bug system. Daniel
[PHP-DOC] cvs: phpdoc /en/functions array.xml
danbeck Mon Jul 2 12:52:11 2001 EDT
Modified files:
/phpdoc/en/functionsarray.xml
Log:
fixing usort example (oops)
Index: phpdoc/en/functions/array.xml
diff -u phpdoc/en/functions/array.xml:1.72 phpdoc/en/functions/array.xml:1.73
--- phpdoc/en/functions/array.xml:1.72 Sat Jun 23 16:10:51 2001
+++ phpdoc/en/functions/array.xml Mon Jul 2 12:52:10 2001
@@ -3062,7 +3062,7 @@
programlisting role=php
function cmp ($a, $b) {
if ($a == $b) return 0;
-return ($a $b) ? -1 : 1;
+return ($a $b) ? -1 : 1;
}
$a = array (3, 2, 5, 6, 1);
Re: [PHP-DOC] cvs: phpdoc /en/functions array.xml
Doh! Sorry about that. It was a quick change and I didn't even do a 'make
test'. I already knew that.. just left my brain at home today.
Daniel
- Original Message -
From: Egon Schmid [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 02, 2001 2:44 PM
Subject: [PHP-DOC] cvs: phpdoc /en/functions array.xml
eschmid Mon Jul 2 15:44:45 2001 EDT
Modified files:
/phpdoc/en/functions array.xml
Log:
Never use a character in examples or ordinary text.
Index: phpdoc/en/functions/array.xml
diff -u phpdoc/en/functions/array.xml:1.73
phpdoc/en/functions/array.xml:1.74
--- phpdoc/en/functions/array.xml:1.73 Mon Jul 2 12:52:10 2001
+++ phpdoc/en/functions/array.xml Mon Jul 2 15:44:44 2001
@@ -3062,7 +3062,7 @@
programlisting role=php
function cmp ($a, $b) {
if ($a == $b) return 0;
-return ($a $b) ? -1 : 1;
+return ($a lt; $b) ? -1 : 1;
}
$a = array (3, 2, 5, 6, 1);
[PHP-DOC] cvs: phpdoc /en/functions filesystem.xml
danbeck Thu Jun 28 11:46:50 2001 EDT Modified files: /phpdoc/en/functionsfilesystem.xml Log: reverted changed made in revision 1.70, added note to clarify when http redirects began to be supported Index: phpdoc/en/functions/filesystem.xml diff -u phpdoc/en/functions/filesystem.xml:1.71 phpdoc/en/functions/filesystem.xml:1.72 --- phpdoc/en/functions/filesystem.xml:1.71 Wed Jun 27 02:53:54 2001 +++ phpdoc/en/functions/filesystem.xml Thu Jun 28 11:46:49 2001 @@ -1145,6 +1145,10 @@ request in order to handle name-based virtual hosts. /simpara simpara + Versions prior to PHP 4.0.5 do not handle HTTP redirects. Because + of this, directories must include trailing slashes. +/simpara +simpara If parameterfilename/parameter begins with ftp://; (not case sensitive), an ftp connection to the specified server is opened and a pointer to the requested file is returned. If the server @@ -2291,6 +2295,10 @@ (not case sensitive), an HTTP 1.0 connection is opened to the specified server and the text of the response is written to standard output. +/para +para + Versions prior to PHP 4.0.5 do not handle HTTP redirects. Because + of this, directories must include trailing slashes. /para para If parameterfilename/parameter begins with ftp://;
Re: [PHP-DOC] cvs: phpdoc /en/functions filesystem.xml
Well, I would, but the cvs repository seems inaccessable to me. I've gotten connection refused errors since this morning. Daniel - Original Message - From: [EMAIL PROTECTED] Newsgroups: php.doc To: [EMAIL PROTECTED] Sent: Wednesday, June 27, 2001 5:12 AM Subject: Re: [PHP-DOC] cvs: phpdoc /en/functions filesystem.xml - Does not handle HTTP redirects, so you must include trailing - slashes on directories. -/simpara -simpara Not everybody runs 4.0.5 yet, maybe it's better to just say that it didn't work till 404? Jeroen
[PHP-DOC] cvs: phpdoc /en/functions zip.xml
danbeck Wed Jun 27 03:55:16 2001 EDT Modified files: /phpdoc/en/functionszip.xml Log: added note about zip support prior to 4.0.7 Index: phpdoc/en/functions/zip.xml diff -u phpdoc/en/functions/zip.xml:1.4 phpdoc/en/functions/zip.xml:1.5 --- phpdoc/en/functions/zip.xml:1.4 Mon Jun 4 00:30:47 2001 +++ phpdoc/en/functions/zip.xml Wed Jun 27 03:55:15 2001 @@ -21,6 +21,12 @@ configuration option when compiling PHP to enable zip support. This module requires ZZIPlib version gt;= 0.10.6. /para + note + para + Zip support before PHP 4.0.7 is experimental. This section + reflects the Zip extension as it exists in PHP 4.0.7 and later. + /para + /note sect1 id=zip-example titleExample Usage/title
[PHP-DOC] cvs: phpdoc /en/functions math.xml
danbeck Wed Jun 27 04:17:25 2001 EDT Modified files: /phpdoc/en/functionsmath.xml Log: odd place for a period Index: phpdoc/en/functions/math.xml diff -u phpdoc/en/functions/math.xml:1.33 phpdoc/en/functions/math.xml:1.34 --- phpdoc/en/functions/math.xml:1.33 Tue Jun 26 22:46:01 2001 +++ phpdoc/en/functions/math.xmlWed Jun 27 04:17:25 2001 @@ -1,6 +1,6 @@ reference id=ref.math titleMathematical Functions/title - titleabbrevMath./titleabbrev + titleabbrevMath/titleabbrev partintro sect1 id=math.intro
[PHP-DOC] cvs: phpdoc /en/chapters config.xml /en/functions info.xml
danbeck Wed Jun 27 05:52:38 2001 EDT Modified files: /phpdoc/en/chapters config.xml /phpdoc/en/functionsinfo.xml Log: documented issue in bug #5827 Index: phpdoc/en/chapters/config.xml diff -u phpdoc/en/chapters/config.xml:1.14 phpdoc/en/chapters/config.xml:1.15 --- phpdoc/en/chapters/config.xml:1.14 Tue Jun 19 22:08:13 2001 +++ phpdoc/en/chapters/config.xml Wed Jun 27 05:52:38 2001 @@ -476,9 +476,15 @@ listitem para This sets the maximum time in seconds a script is allowed to - take before it is terminated by the parser. This helps + run before it is terminated by the parser. This helps prevent poorly written scripts from tying up the server. The - default setting is literal30/literal. + default setting is literal30/literal. + /para + para +The maximum execution time is not affected by system calls, +the functionsleep/function function, etc. Please see the +functionset_time_limit/function function for more +details. /para /listitem /varlistentry Index: phpdoc/en/functions/info.xml diff -u phpdoc/en/functions/info.xml:1.51 phpdoc/en/functions/info.xml:1.52 --- phpdoc/en/functions/info.xml:1.51 Tue Jun 26 13:24:50 2001 +++ phpdoc/en/functions/info.xmlWed Jun 27 05:52:38 2001 @@ -1390,10 +1390,10 @@ simpara Set the number of seconds a script is allowed to run. If this is reached, the script returns a fatal error. The default limit is - 30 seconds or, if it exists, the max_execution_time value defined - in the link linkend=configuration.fileconfiguration - file/link. If seconds is set to zero, no time limit is - imposed. + 30 seconds or, if it exists, the + literalmax_execution_time/literal value defined in the link + linkend=ini.max-execution-timeconfiguration file/link. If + seconds is set to zero, no time limit is imposed. /simpara simpara When called, functionset_time_limit/function restarts the @@ -1403,11 +1403,24 @@ total of 45 seconds before timing out. /simpara simpara - Note that functionset_time_limit/function has no effect when + functionset_time_limit/function has no effect when PHP is running in safe mode. There is no workaround other than turning off safe mode or changing the time limit in the link - linkend=configuration.fileconfiguration file/link. + linkend=ini.max-execution-timeconfiguration file/link. /simpara +note + para + The functionset_time_limit/function function and the + configuration directive link + linkend=ini.max-execution-timemax_execution_time/link only + affect the execution time of the script itself. Any time spent + on activity that happens outside the execution of the script + such as system calls using functionsystem/function, the + functionsleep/function function, database queries, etc. is + not included when determining the maximum time that the script + has been running. + /para +/note /refsect1 /refentry
[PHP-DOC] cvs: phpdoc /en/functions java.xml
danbeck Tue Jun 26 16:08:25 2001 EDT Modified files: /phpdoc/en/functionsjava.xml Log: additional grammer correction Index: phpdoc/en/functions/java.xml diff -u phpdoc/en/functions/java.xml:1.4 phpdoc/en/functions/java.xml:1.5 --- phpdoc/en/functions/java.xml:1.4Tue Jun 26 06:25:28 2001 +++ phpdoc/en/functions/java.xmlTue Jun 26 16:08:25 2001 @@ -4,12 +4,12 @@ partintro para There are two possible ways to bridge PHP and Java: you can either -integrate Java into PHP or, which is the more stable and efficient -solution, integrate PHP into a Java Servlet environment. +integrate Java into PHP, which is the more stable and efficient +solution, or integrate PHP into a Java Servlet environment. The former is provided by ext/java, the latter by a SAPI module that interfaces with the Servlet server. /para -para + para PHP 4 ext/java provides a simple and effective means for creating and invoking methods on Java objects from PHP. The JVM is created using JNI, and everything runs in-process. Build instructions for ext/java can be
Re: [PHP-DOC] Convention: true/false
I personally don't care for one over the other. I would only prefer that we are consistant and that it's rendered properly in the various manual formats. Daniel - Original Message - From: Jeroen van Wolffelaar [EMAIL PROTECTED] To: Hojtsy Gabor [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; PHP-DOC lista [EMAIL PROTECTED] Sent: Tuesday, June 26, 2001 4:26 AM Subject: Re: [PHP-DOC] Convention: true/false TRUE *is not* a constant. There is a boolean type in PHP 4. TRUE *was* a constant in PHP 3... It is still defined as constant, just like NULL. (zend_constants.c:117 : true/false constants) THough you can argue that it's better to see it as being a special keyword. It is a constant in the sense that its value never changes. And, though layout shouldn't be an issue when it comes to xml, I like the makeup op constant better in case of values like true... So, I'm still in favor of constant. Thats 1 contra, 1 pro. Goba Jeroen van Wolffelaar [EMAIL PROTECTED] http://www.A-Eskwadraat.nl/~jeroen
Re: [PHP-DOC] cvs: phpdoc /en/functions var.xml
I don't think it's necessary to quote the developers when writing
documentation. Many people probably have no idea who Andi is and it's even
(very remotely) possible that he may not be involved in PHP development in
the future. The PHP docs are the definitive source for PHP documentation
and they already indirectly reflect the ideas and thoughts of the
development team, without having to quote them. Besides, the documentation
should be written in a confident style without having to support itself with
quotes or references.
What do you guys think?
Daniel
- Original Message -
From: Zak Greant [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, June 24, 2001 12:11 AM
Subject: [PHP-DOC] cvs: phpdoc /en/functions var.xml
zak Sun Jun 24 07:11:35 2001 EDT
Modified files:
/phpdoc/en/functions var.xml
Log:
Added note on behavior of is_scalar() with regards to resource type
values
Index: phpdoc/en/functions/var.xml
diff -u phpdoc/en/functions/var.xml:1.54 phpdoc/en/functions/var.xml:1.55
--- phpdoc/en/functions/var.xml:1.54 Sat Jun 23 22:10:51 2001
+++ phpdoc/en/functions/var.xml Sun Jun 24 07:11:35 2001
@@ -747,6 +747,14 @@
/para
note
para
+ Note that the PHP resource type is not considered a scalar value.
+ Andi Gutmans states: [Resources] are abstract datatypes which
+ happen to be in ID (integer) form ... people should [not] count
+ on it being an integer as this could change one day.
+ /para
+/note
+note
+ para
This function was added to the CVS code after the release of PHP
4.0.4pl1
/para
@@ -1291,7 +1299,7 @@
lt;?php
$a = array (1, 2, array (a, b, c));
var_dump ($a);
-
+
/* output:
array(3) {
[0]=
Re: [PHP-DOC] cvs: phpdoc /en/functions var.xml
Perfect, I think it conveys the idea even better than the first version. Thanks, Daniel - Original Message - From: Zak Greant [EMAIL PROTECTED] To: Hojtsy Gabor [EMAIL PROTECTED]; Daniel Beckham [EMAIL PROTECTED]; [EMAIL PROTECTED]; Rasmus Lerdorf [EMAIL PROTECTED] Sent: Sunday, June 24, 2001 11:50 AM Subject: Re: [PHP-DOC] cvs: phpdoc /en/functions var.xml Good point - thanks! :) How is this? para functionis_scalar/function does not consider resource type values to be scalar values. This behavior is intentional: Resources are abstract datatypes which are currently based on integers. This implementation detail should not be relied upon, as it may change. /para --zak Daniel Beckham wrote: I don't think it's necessary to quote the developers when writing documentation. Many people probably have no idea who Andi is and it's even (very remotely) possible that he may not be involved in PHP development in the future. The PHP docs are the definitive source for PHP documentation and they already indirectly reflect the ideas and thoughts of the development team, without having to quote them. Besides, the documentation should be written in a confident style without having to support itself with quotes or references.
[PHP-DOC] Re: [php-cvs] cvs: phpdoc /en/functions filesystem.xml
Hey, I just fixed a small typo where you had of instead of off, but I was wondering if maybe that sentence could be a litte bit clearer? How about: If the optional parameter parametersuffix/parameter is supplied, parametersuffix/parameter will be removed from the end of the filename before it is returned. /para /note para the parametersuffix/parameter parameter was added in PHP 4.0.7. /para /note I didn't want to be rude and alter a change you just commited... Daniel - Original Message - From: Hartmut Holzgraefe [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 22, 2001 8:09 PM Subject: [php-cvs] cvs: phpdoc /en/functions filesystem.xml hholzgra Sat Jun 23 03:09:51 2001 EDT Modified files: /phpdoc/en/functions filesystem.xml Log: version info for new parameter Index: phpdoc/en/functions/filesystem.xml diff -u phpdoc/en/functions/filesystem.xml:1.66 phpdoc/en/functions/filesystem.xml:1.67 --- phpdoc/en/functions/filesystem.xml:1.66 Sat Jun 23 02:56:33 2001 +++ phpdoc/en/functions/filesystem.xml Sat Jun 23 03:09:51 2001 @@ -22,7 +22,8 @@ Given a string containing a path to a file, this function will return the base name of the file. If the filename ends in parametersuffix/parameter this will - also be cut of. + also be cut of (the parametersuffix/parameter parameter was added + in PHP 4.0.7). /para para On Windows, both slash (literal//literal) and backslash
[PHP-DOC] Re: [php-cvs] cvs: phpdoc / manual.xml.in /en/functions printer.xml
heh, I was wondering why there was an entry in manual.xml.in, but no printer.xml file to go with it... Daniel - Original Message - From: Hartmut Holzgraefe [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 22, 2001 4:59 AM Subject: [php-cvs] cvs: phpdoc / manual.xml.in /en/functions printer.xml hholzgra Fri Jun 22 11:59:28 2001 EDT Modified files: /phpdoc manual.xml.in /phpdoc/en/functions printer.xml Log: reverting the removal of printer.xml r1.1 i can't see any errors produced by this file and it is definetly *not* a PEAR package but a native extension for Win32 systems
[PHP-DOC] List messages are being delayed?
For some reason, it seems that messages sent to the lists aren't being delivered for over 5 hours or more. I only just got a message that I sent today at 11:30AM. Although, they do show up on the news server pretty quickly. Is anyone else experiencing this? Daniel
Re: [PHP-DOC] knock knock
Yes, it does seem to be alive again. Daniel - Original Message - From: Damien Seguy [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 3:26 AM Subject: [PHP-DOC] knock knock Hi, is this mailing list awaken? Dams
[PHP-DOC] cvs: phpdoc /en/functions pdf.xml
danbeck Wed May 23 09:07:45 2001 EDT Modified files: /phpdoc/en/functionspdf.xml Log: removed a mysterious empty row in the compatibility table Index: phpdoc/en/functions/pdf.xml diff -u phpdoc/en/functions/pdf.xml:1.53 phpdoc/en/functions/pdf.xml:1.54 --- phpdoc/en/functions/pdf.xml:1.53Mon May 21 13:17:16 2001 +++ phpdoc/en/functions/pdf.xml Wed May 23 09:07:45 2001 @@ -218,10 +218,6 @@ literalimageheight/literal as the second parameter and the image as the third parameter./entry /row -row - entryfunction/function/entry - entryfunction/function/entry -/row /tbody /tgroup /table
[PHP-DOC] MacOS filename length and downloadable manuals
I've noticed a couple of bug reports (#10445, #10862) about the filenames being too large for MacOS users in the downloadable manual. I know this is in no way a trivial thing to fix, but what do we need to do with the bug reports themselves? Should they be left open until this can be fixed sometime in the future? Or closed to keep the bug system uncluttered? (as if that could be done, hehe) Daniel
[PHP-DOC] cvs: phpdoc /en/functions image.xml
danbeck Tue May 22 07:33:47 2001 EDT Modified files: /phpdoc/en/functionsimage.xml Log: corrected xml problem that was causing m Index: phpdoc/en/functions/image.xml diff -u phpdoc/en/functions/image.xml:1.41 phpdoc/en/functions/image.xml:1.42 --- phpdoc/en/functions/image.xml:1.41 Tue May 22 02:21:40 2001 +++ phpdoc/en/functions/image.xml Tue May 22 07:33:46 2001 @@ -2166,7 +2166,7 @@ ImageJpeg($im, , 100);//for best quality... your mileage may vary ImageDestroy ($im); ?gt; - /programlisting role=php + /programlisting /para para See also functionImagePSFreeFont/function.
[PHP-DOC] cvs: phpdoc /en/functions mail.xml
danbeck Tue May 22 07:36:42 2001 EDT Modified files: /phpdoc/en/functionsmail.xml Log: changed cc and bcc back the correct case (oops) Index: phpdoc/en/functions/mail.xml diff -u phpdoc/en/functions/mail.xml:1.19 phpdoc/en/functions/mail.xml:1.20 --- phpdoc/en/functions/mail.xml:1.19 Mon May 21 19:13:37 2001 +++ phpdoc/en/functions/mail.xmlTue May 22 07:36:41 2001 @@ -127,8 +127,8 @@ /* If you want to send html mail, uncomment the following line */ // $headers .= Content-Type: text/html; charset=iso-8859-1\n; // Mime type -$headers .= Cc: [EMAIL PROTECTED]\n; // CC to -$headers .= Bcc: [EMAIL PROTECTED], [EMAIL PROTECTED]\n; // BCCs to +$headers .= cc: [EMAIL PROTECTED]\n; // CC to +$headers .= bcc: [EMAIL PROTECTED], [EMAIL PROTECTED]\n; // BCCs to /* and now mail it */ mail($recipient, $subject, $message, $headers);
[PHP-DOC] cvs: phpdoc / configure.in
danbeck Tue May 22 09:56:38 2001 EDT Modified files: /phpdoc configure.in Log: added location of docbook stylesheets for redhat 7.1 users (and the new docbook update) Index: phpdoc/configure.in diff -u phpdoc/configure.in:1.66 phpdoc/configure.in:1.67 --- phpdoc/configure.in:1.66Thu May 17 05:35:38 2001 +++ phpdoc/configure.in Tue May 22 09:56:37 2001 @@ -1,4 +1,4 @@ -dnl $Id: configure.in,v 1.66 2001/05/17 12:35:38 martin Exp $ +dnl $Id: configure.in,v 1.67 2001/05/22 16:56:37 danbeck Exp $ AC_INIT(global.ent) @@ -61,6 +61,7 @@ /usr/share/sgml/docbk30/dsl \ /usr/share/sgml/docbkdsl \ /usr/share/sgml/stylesheets/docbook \ + /usr/share/sgml/docbook/dsssl-stylesheets \ /usr/local/lib/dsssl/stylesheets/docbook \ /usr/local/lib/dsssl/stylesheets/nwalsh-modular \ /usr/local/lib/sgml/stylesheets/docbook \
Re: [PHP-DOC] Casing function names: Conclusion = ?
I would normally say yes to lowercasing all function names, (and I argued for it last week) but I have to agree with Egon here. I think that making all function names lowercase will limit the readability of certain function libraries. The most obvious example is the Image functions. I think we need to create more readable function aliases and then re-document those instead. In the end, we are producing a document for the PHP public and making it diffcult for them to read function names here in the docs and in their code is a bit of a disservice. Just as much as not having function names hyperlinked. IMHO Daniel - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, May 22, 2001 7:16 PM Subject: Re: [PHP-DOC] Casing function names: Conclusion = ? On Wed, May 23, 2001 at 01:27:18AM +0200, [EMAIL PROTECTED] wrote: All function names in the docs should be lowercase for consistence. No matter where in the sentence, or how unreadable the function will be. I'm against this. It would result in unreadable and bad to remember function names. For unreadable func-names, a longer-term renaming would be nice. But first, get the manual lowercase. Then those php.dev guys will just need to rename, because we are NOT going to write it mixed case anymore for readability. I would recommend to make aliases in the source code first. After that we should the change the function names in the manuals. Just only react if you strongly disagree. If nobody strongly disagrees, I'll commit the changes somewhere in the next week. Thanks to Torben's script, and including the refentry stuff etc. I have nothing against Torben, he has also read about my fight with some core developers and now the mysql_*() functions are more readable. You can also use the old syntax. The original functions havent been removed yet. -Egon -- LinuxTag, Stuttgart, Germany: July 5-8 2001: http://www.linuxtag.de/ All known books about PHP and related books: http://php.net/books.php Concert Band of the University of Hohenheim: http://www.concert-band.de/ First and second bestselling book in German: http://www.php-buch.de/
Re: [PHP-DOC] Function References not showing up in docs for mixed case function names
From what I gather it will most likely take place in 4.1.x and there will be a switch to turn this on or off. (Probably on by default.) I think this is a great move and will be glad to see it happen. Daniel - Original Message - From: Stig Sæther Bakken [EMAIL PROTECTED] To: James Moore [EMAIL PROTECTED] Cc: 'Lars Torben Wilson' [EMAIL PROTECTED]; 'Daniel Beckham' [EMAIL PROTECTED]; 'phpdoc' [EMAIL PROTECTED] Sent: Monday, May 21, 2001 4:04 AM Subject: Re: [PHP-DOC] Function References not showing up in docs for mixed case function names [James Moore [EMAIL PROTECTED]] bad: Foo() does bar; good: The function foo() does bar. Daniel I agree with your second assertion. I could see a lot of users getting confused if the first were followed blindly, though (say, if one was documenting C). Which is one reason (besides style) why I agree with the second assertion...:) Im sorry but I feel we should keep all function names lowercase. Take a look at http://php.net/manual/en/ref.pdf.php now, that really looks ugly too me, there is no reason to have function names at beginning of sentences and lets keep the manual consistent, if its all lowercase we will encourage people to name their functions properly etc, we are not going to start putting PdF_OpeN in the manual just because its supported lets keep the manual consistent and keep it lowercase, this has worked for the past x years and there is no real reason to change it. Just a comment from the side here: keep in mind that there has been discussion on php-dev about making PHP functions and classes case sensitive in a future release. It won't happen tomorrow, but it's something to store in ones subconsciousness. - Stig -- Stig Sæther Bakken [EMAIL PROTECTED] Fast Search Transfer ASA, Trondheim, Norway
[PHP-DOC] cvs: phpdoc /en/functions pdf.xml
danbeck Mon May 21 12:28:59 2001 EDT Modified files: /phpdoc/en/functionspdf.xml Log: corrected doc bug #10586 (pdf_stringwidth proto and definition were incorrect Index: phpdoc/en/functions/pdf.xml diff -u phpdoc/en/functions/pdf.xml:1.51 phpdoc/en/functions/pdf.xml:1.52 --- phpdoc/en/functions/pdf.xml:1.51Sun May 20 20:36:19 2001 +++ phpdoc/en/functions/pdf.xml Mon May 21 12:28:58 2001 @@ -2738,13 +2738,29 @@ funcdefdouble functionpdf_stringwidth/function/funcdef paramdefint parameterpdf object/parameter/paramdef paramdefstring parametertext/parameter/paramdef - paramdefstring parameteroptionaltext/optional/parameter/paramdef - paramdefstring parameteroptionaltext/optional/parameter/paramdef + paramdefint parameteroptionalfont/optional/parameter/paramdef + paramdefdouble parameteroptionalsize/optional/parameter/paramdef /funcprototype /funcsynopsis para - Return the width of text in an arbitrary font. + Returns the width of parametertext/parameter using the last + font set by functionpdf_setfont/function. If the optional + parameters parameterfont/parameter and + parametersize/parameter are specified, the width will be + calculated using that font and size instead. Please note that + parameterfont/parameter is a font handle returned by + functionpdf_findfont/function. /para + note +para + Both the parameterfont/parameter and parametersize/parameter + parameters must used together. +/para + /note + para +See Also: functionpdf_setfont/function and +functionpdf_findfont/function. + /para /refsect1 /refentry
[PHP-DOC] cvs: phpdoc /en/functions misc.xml
danbeck Mon May 21 12:36:19 2001 EDT Modified files: /phpdoc/en/functionsmisc.xml Log: corrected the exit() documentation to better represent what it does Index: phpdoc/en/functions/misc.xml diff -u phpdoc/en/functions/misc.xml:1.42 phpdoc/en/functions/misc.xml:1.43 --- phpdoc/en/functions/misc.xml:1.42 Sat May 19 13:46:56 2001 +++ phpdoc/en/functions/misc.xmlMon May 21 12:36:19 2001 @@ -394,12 +394,13 @@ funcsynopsis funcprototype funcdefvoid functionexit/function/funcdef - void/ + paramdefstring parametermessage/parameter/paramdef /funcprototype /funcsynopsis simpara - This language construct terminates parsing of the script.It - does not return. + The functionexit/function function terminates parsing of the + script. It has no return value, but will echo + parametermessage/parameter to STDOUT. (i.e. the browser) /simpara simpara See also functiondie/function.
Re: [PHP-DOC] cvs: phpdoc /en/functions misc.xml
I'll make that change then. Daniel - Original Message - From: [EMAIL PROTECTED] Newsgroups: php.doc To: [EMAIL PROTECTED] Sent: Monday, May 21, 2001 3:42 PM Subject: Re: [PHP-DOC] cvs: phpdoc /en/functions misc.xml It does not terminate parsing, just executing. A function definition after a exit statement WILL be read, and that function CAN be used. (before the exit, that is ;) Gr, Jeroen Daniel Beckham [EMAIL PROTECTED] wrote in message cvsdanbeck990473779@cvsserver">news:cvsdanbeck990473779@cvsserver... danbeck Mon May 21 12:36:19 2001 EDT Modified files: /phpdoc/en/functions misc.xml Log: corrected the exit() documentation to better represent what it does Index: phpdoc/en/functions/misc.xml diff -u phpdoc/en/functions/misc.xml:1.42 phpdoc/en/functions/misc.xml:1.43 --- phpdoc/en/functions/misc.xml:1.42 Sat May 19 13:46:56 2001 +++ phpdoc/en/functions/misc.xml Mon May 21 12:36:19 2001 @@ -394,12 +394,13 @@ funcsynopsis funcprototype funcdefvoid functionexit/function/funcdef - void/ + paramdefstring parametermessage/parameter/paramdef /funcprototype /funcsynopsis simpara - This language construct terminates parsing of the script.It - does not return. + The functionexit/function function terminates parsing of the + script. It has no return value, but will echo + parametermessage/parameter to STDOUT. (i.e. the browser) /simpara simpara See also functiondie/function.
[PHP-DOC] cvs: phpdoc /en/functions misc.xml
danbeck Mon May 21 13:52:21 2001 EDT Modified files: /phpdoc/en/functionsmisc.xml Log: corrected explanation of exit Index: phpdoc/en/functions/misc.xml diff -u phpdoc/en/functions/misc.xml:1.43 phpdoc/en/functions/misc.xml:1.44 --- phpdoc/en/functions/misc.xml:1.43 Mon May 21 12:36:19 2001 +++ phpdoc/en/functions/misc.xmlMon May 21 13:52:21 2001 @@ -398,7 +398,7 @@ /funcprototype /funcsynopsis simpara - The functionexit/function function terminates parsing of the + The functionexit/function function terminates execution of the script. It has no return value, but will echo parametermessage/parameter to STDOUT. (i.e. the browser) /simpara
[PHP-DOC] cvs: phpdoc /en/functions mail.xml
danbeck Mon May 21 19:13:37 2001 EDT Modified files: /phpdoc/en/functionsmail.xml Log: another change for doc bug #9859 Index: phpdoc/en/functions/mail.xml diff -u phpdoc/en/functions/mail.xml:1.18 phpdoc/en/functions/mail.xml:1.19 --- phpdoc/en/functions/mail.xml:1.18 Sun May 20 19:59:47 2001 +++ phpdoc/en/functions/mail.xmlMon May 21 19:13:37 2001 @@ -30,10 +30,11 @@ /funcprototype /funcsynopsis simpara - functionMail/function automatically mails the message specified - in parametermessage/parameter to the receiver specified in - parameterto/parameter. Multiple recipients can be specified by - putting a comma between each address in parameterto/parameter. + functionMail/function automatically mails the message + specified in parametermessage/parameter to the receiver + specified in parameterto/parameter. Multiple recipients can + be specified by putting a comma between each address in + parameterto/parameter. /simpara para functionmail/function returns literalTRUE/literal if the mail @@ -51,6 +52,14 @@ the end of the header. This is typically used to add extra headers. Multiple extra headers are separated with a newline. /simpara +note + para + On Win32 systems, you must use literal\r\n/literal to + seperate headers. Please also note that the cc: and bcc: headers + are case sensitve and should be written as literalCc:/literal + and literalBcc:/literal on Win32 systems. + /para +/note simpara If the fifth parameter is supplied, PHP will add this data to the call to the mailer. This is useful when setting the
Re: [PHP-DOC] Function References not showing up in docs for mixed case function names
Same here, acutally. I was making some changes to the PDF functions the other day and noticed the links not working. I always write in lower case. It just makes the most sense to me. Daniel - Original Message - From: Lars Torben Wilson [EMAIL PROTECTED] To: Hojtsy Gabor [EMAIL PROTECTED] Cc: Daniel Beckham [EMAIL PROTECTED]; phpdoc [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, May 20, 2001 4:56 AM Subject: Re: [PHP-DOC] Function References not showing up in docs for mixed case function names Hojtsy Gabor writes: by Daniel: I would propose that a phpdoc wide change be made so that all functions are written in lowercase form. It's not necessary to have them in a mixed case created on the author's whim. by Jeroen: function-names are NOT case-sensitive in PHP itself... so why not change the stylesheets or something so that it is NOT case-sensitive in the docs either? We've got an excellent DSSSL-fu'er over here :), maybe he or someone else knows how to change that? XML *IS* case sensitive, and we use XML to make the docs. So I think we should be XML compatible with function names too. Goba True, but the tool used to document another tool should not define what is presented to the reader. :) I took a quick look through the DSSSL before I committed the patch which lowercased the Hyperwave function tags a couple of days ago, and it looked as though case-folding was intended, as did the XSL stylesheet. I haven't had time to look up the syntax used and I'm not an expert in either though, so I couldn't say for sure and just ended up running a script over hw.xml to fix the problem. To be honest, I've never noticed this problem before, and I've been working on the manual for 3 years. But then, I always use lowercase for function names so I wouldn't necessarily have clued in before now. :) -- Torben Wilson [EMAIL PROTECTED] http://www.thebuttlesschaps.com +1.604.709.0506
Re: [PHP-DOC] Function References not showing up in docs for mixed case function names
Hmm.. if you are going to do this in an automated way, you need to look at refname/refname tags also. Those show up on the intro and sidebar nav areas. Daniel - Original Message - From: [EMAIL PROTECTED] Newsgroups: php.doc To: [EMAIL PROTECTED] Sent: Sunday, May 20, 2001 6:49 AM Subject: Re: [PHP-DOC] Function References not showing up in docs for mixed case function names XML *IS* case sensitive, and we use XML to make the docs. So I think we should be XML compatible with function names too. True, but the tool used to document another tool should not define what is presented to the reader. :) I agree, but for a little consistance it would still be a good idea to make anything lowercase... this can't be too hard, just a regular expression to find all function.../function's, and then make it lowercase? Or that script, maybe that works well? And that even at the start of a sentence. You also don't write numbers in uppercase just because they happen to be the first 'word' of a sentence. In a day or something I'll process the whole documentation (all languages too). Unless someone has any objections of course. Greetz, Jeroen
Re: [PHP-DOC] Function References not showing up in docs for mixed case function names
As far as English grammar goes, they should be capitalized if they are the first word in a sentence. If you are using the function name as the first word though, you probably could come up with a better way to write it. bad: Foo() does bar; good: The function foo() does bar. Daniel - Original Message - From: Lars Torben Wilson [EMAIL PROTECTED] Newsgroups: php.doc To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, May 20, 2001 7:09 AM Subject: Re: [PHP-DOC] Function References not showing up in docs for mixed case function names And that even at the start of a sentence. You also don't write numbers in uppercase just because they happen to be the first 'word' of a sentence. Bad example: sentences shouldn't start with digits anyway. Spell the word out at the start of a sentence. It remains largely undecided as to whether function names should be capitalized when starting a sentence--I personally believe they should not be, but not everybody thinks that way. :)
Re: [PHP-DOC] Function References not showing up in docs for mixed case function names
- Original Message - From: [EMAIL PROTECTED] To: Lars Torben Wilson [EMAIL PROTECTED]; Hojtsy Gabor [EMAIL PROTECTED] Cc: Daniel Beckham [EMAIL PROTECTED]; phpdoc [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, May 20, 2001 1:23 PM Subject: Re: [PHP-DOC] Function References not showing up in docs for mixed case function names This problem with the functions names have been discussed several times. Look at the mysql_*() functions, there is everything ok. Zeev made aliases so we have now easy functions name which can be rememberd by any average user. Sure function names are case-insensitive. But can you imagine to rename a function like ImageCopyMerge() or ImageCopyResampled() to imagecopymerge() or imagecopyresampled()? It took me a few minutes to understand what you were saying, but I see now that you mean that it's difficult to read those long function names in code. What does it take to add aliases for these functions? Is having this many function aliases ok with the development team, etc.? If this is truly an issue, can we begin making these transitions? Daniel
Re: [PHP-DOC] Function References not showing up in docs for mixed case function names
You are preaching to the choir. =) I think the obstacle here is the need for the development/qa team to make the necessary changes and implement the necessary standards. As Egon said... we write documentation and don't necessarily have the time or the know-how to make these changes. Daniel - Original Message - From: Hojtsy Gabor [EMAIL PROTECTED] To: Daniel Beckham [EMAIL PROTECTED]; phpdoc [EMAIL PROTECTED] Sent: Sunday, May 20, 2001 3:19 PM Subject: Re: [PHP-DOC] Function References not showing up in docs for mixed case function names There should be a function naming standard for all functions... Goba ... . . . . . Editor of the Hungarian PHP manual, Admin of the Hungarian PHP mirror
[PHP-DOC] cvs: phpdoc / global.ent
danbeck Sun May 20 15:34:58 2001 EDT Modified files: /phpdoc global.ent Log: added ent for ZZIPlib homepage Index: phpdoc/global.ent diff -u phpdoc/global.ent:1.93 phpdoc/global.ent:1.94 --- phpdoc/global.ent:1.93 Thu May 17 13:22:34 2001 +++ phpdoc/global.ent Sun May 20 15:34:57 2001 @@ -1,6 +1,6 @@ !-- -*- SGML -*- - $Id: global.ent,v 1.93 2001/05/17 20:22:34 danbeck Exp $ + $Id: global.ent,v 1.94 2001/05/20 22:34:57 danbeck Exp $ Contains global macros for all the SGML documents. @@ -151,6 +151,7 @@ !ENTITY url.yaz-phpyaz http://www.indexdata.dk/phpyaz/; !ENTITY url.zend http://www.zend.com/; !ENTITY url.zlib http://www.info-zip.org/pub/infozip/zlib/; +!ENTITY url.zziplib http://zziplib.sourceforge.net/; !ENTITY book.applied.cryptography 'Applied Cryptography by Schneier (ISBN 0-471-11709-9)'
[PHP-DOC] cvs: phpdoc /en/chapters install.xml
danbeck Sun May 20 15:48:47 2001 EDT Modified files: /phpdoc/en/chapters install.xml Log: zziplib typo and corrected some bzip2 stuff (it indicated that bzip2 was supported by PHP 3 when it's not... Index: phpdoc/en/chapters/install.xml diff -u phpdoc/en/chapters/install.xml:1.61 phpdoc/en/chapters/install.xml:1.62 --- phpdoc/en/chapters/install.xml:1.61 Sun May 20 15:36:00 2001 +++ phpdoc/en/chapters/install.xml Sun May 20 15:48:47 2001 @@ -2236,13 +2236,13 @@ /listitem /varlistentry - varlistentry id=install.configure.with-bzip2-dir + varlistentry id=install.configure.with-bzip2 term parameter--with-bz2[=DIR]/parameter /term listitem para -PHP 3, PHP 4: Include support bzip2. DIR +PHP 4: Include support bzip2. DIR is the bzip2 install dir. /para /listitem @@ -2274,9 +2274,9 @@ /listitem /varlistentry - varlistentry id=install.configure.with-zzlib + varlistentry id=install.configure.with-zziplib term - parameter--with-zzlib[=DIR]/parameter + parameter--with-zziplib[=DIR]/parameter /term listitem para
[PHP-DOC] cvs: phpdoc /en/functions bzip2.xml
danbeck Sun May 20 15:49:49 2001 EDT Modified files: /phpdoc/en/functionsbzip2.xml Log: added a link to the configuration option in install.xml and corrected a minor typo Index: phpdoc/en/functions/bzip2.xml diff -u phpdoc/en/functions/bzip2.xml:1.5 phpdoc/en/functions/bzip2.xml:1.6 --- phpdoc/en/functions/bzip2.xml:1.5 Thu Mar 15 03:13:40 2001 +++ phpdoc/en/functions/bzip2.xml Sun May 20 15:49:49 2001 @@ -8,9 +8,9 @@ transparently read and write bzip2 (.bz2) compressed files. /para para -bzip2 support in PHP is not enabled by default. You will need to -use the parameter--with-bz2[=DIR]/parameter configuration -option when compiling php to enable bzip2 support. This module +Bzip2 support in PHP is not enabled by default. You will need to +use the link linkend=install.configure.with-bzip2--with-bz2/link +configuration +option when compiling PHP to enable bzip2 support. This module requires bzip2/libbzip2 version gt;= 1.0.x. /para
Re: [PHP-DOC] Function References not showing up in docs for mixed case function names
hehe, the PDF fuctions were the reason I started this thread in the first place. They should probably all be changed to lowercase sometime after X-Files is over tonight. =) Daniel - Original Message - From: James Moore [EMAIL PROTECTED] To: 'Lars Torben Wilson' [EMAIL PROTECTED]; 'Daniel Beckham' [EMAIL PROTECTED] Cc: 'phpdoc' [EMAIL PROTECTED] Sent: Sunday, May 20, 2001 6:08 PM Subject: RE: [PHP-DOC] Function References not showing up in docs for mixed case function names bad: Foo() does bar; good: The function foo() does bar. Daniel I agree with your second assertion. I could see a lot of users getting confused if the first were followed blindly, though (say, if one was documenting C). Which is one reason (besides style) why I agree with the second assertion...:) Im sorry but I feel we should keep all function names lowercase. Take a look at http://php.net/manual/en/ref.pdf.php now, that really looks ugly too me, there is no reason to have function names at beginning of sentences and lets keep the manual consistent, if its all lowercase we will encourage people to name their functions properly etc, we are not going to start putting PdF_OpeN in the manual just because its supported lets keep the manual consistent and keep it lowercase, this has worked for the past x years and there is no real reason to change it. - James
[PHP-DOC] option tags for configure option links?
I just noticed this in the partintro section of the imap file: option role=configure--with-imap/option It displays as a fixed width font in the online manual, but I'm wondering if it was meant to be linked to the imap configuration section? Currently, the only way I know to link it is to just use a link linkend= tag... Daniel
[PHP-DOC] cvs: phpdoc /en/functions mail.xml
danbeck Sun May 20 19:59:47 2001 EDT Modified files: /phpdoc/en/functionsmail.xml Log: corrected part of doc bug #9859 Index: phpdoc/en/functions/mail.xml diff -u phpdoc/en/functions/mail.xml:1.17 phpdoc/en/functions/mail.xml:1.18 --- phpdoc/en/functions/mail.xml:1.17 Fri May 11 00:31:28 2001 +++ phpdoc/en/functions/mail.xmlSun May 20 19:59:47 2001 @@ -118,8 +118,8 @@ /* If you want to send html mail, uncomment the following line */ // $headers .= Content-Type: text/html; charset=iso-8859-1\n; // Mime type -$headers .= cc:[EMAIL PROTECTED]\n; // CC to -$headers .= bcc:[EMAIL PROTECTED], [EMAIL PROTECTED]\n; // BCCs to +$headers .= Cc: [EMAIL PROTECTED]\n; // CC to +$headers .= Bcc: [EMAIL PROTECTED], [EMAIL PROTECTED]\n; // BCCs to /* and now mail it */ mail($recipient, $subject, $message, $headers);
[PHP-DOC] cvs: phpdoc /en/functions cpdf.xml
danbeck Sun May 20 20:26:27 2001 EDT Modified files: /phpdoc/en/functionscpdf.xml Log: correcting doc bug #10286, reworded information about clibpdf being able to create pdf documents in memory. It looked like someone had tried to remove the comparison between clibpdf and pdflib, but it was confusing. I also removed a lot of the information about clibpdf being faster, etc. than pdflib since it was information from circa pdflib 2.0 and we really aren't trying to promote one over the other. Index: phpdoc/en/functions/cpdf.xml diff -u phpdoc/en/functions/cpdf.xml:1.22 phpdoc/en/functions/cpdf.xml:1.23 --- phpdoc/en/functions/cpdf.xml:1.22 Fri May 18 09:36:48 2001 +++ phpdoc/en/functions/cpdf.xmlSun May 20 20:26:27 2001 @@ -4,29 +4,21 @@ partintro simpara -ClibPDF lets you create PDF documents with PHP. It is available at -ulink url=url.fastio;FastIO/ulink but it isn't free -software. You should definitely read the licence before you start -playing with ClibPDF. If you cannot fullfil the licence agreement -consider using pdflib by Thomas Merz, which is also very powerful. -ClibPDF functionality and API is similar to Thomas Merz's pdflib but, -according to FastIO, ClibPDF is faster and creates smaller documents. -This may have changed with the new version 2.0 of pdflib. A simple -benchmark (the pdfclock.c example from pdflib 2.0 turned into a php -script) actually shows no difference in speed at all. The file size -is also similar if compression is turned off. So, try them both -and see which one does the job for you. + ClibPDF lets you create PDF documents with PHP. It is available for + download from ulink url=url.fastio;FastIO/ulink, but + requires that you purchase a license for commercial use. ClibPDF + functionality and API is similar to link + linkend=ref.pdfPDFlib/link. /simpara simpara This documentation should be read alongside the ClibPDF manual since it explains the library in much greater detail. /simpara - simpara -Many functions in the native ClibPDF and the PHP module, as -well as in pdflib, have the same name. All functions except for -functioncpdf_open/function take the handle for the document as -their first parameter. +Many functions in the native ClibPDF and the PHP module, as well +as in link linkend=ref.pdfPDFlib/link, have the same name. +All functions except for functioncpdf_open/function take the +handle for the document as their first parameter. /simpara simpara Currently this handle is not used internally since ClibPDF does @@ -45,12 +37,13 @@ /simpara /note simpara -One big advantage of ClibPDF over pdflib used to be the possibility -to create -the pdf document completely in memory without using temporary files. -It also provides the ability to pass coordinates in a predefined -unit length. This is a handy feature but can be simulated with -functionpdf_translate/function. + A nice feature of ClibPDF (and link + linkend=ref.pdfPDFlib/link) is the ability to create the pdf + document completely in memory without using temporary files. It + also provides the ability to pass coordinates in a predefined unit + length. (This feature can also be simulated by + functionpdf_translate/function when using the link + linkend=ref.pdfPDFlib/link. functions.) /simpara simpara Another nice feature of ClibPDF is the fact that any page can be modified
[PHP-DOC] cvs: phpdoc /en/functions pdf.xml
danbeck Sun May 20 20:36:19 2001 EDT Modified files: /phpdoc/en/functionspdf.xml Log: corrected doc bug #10335 Index: phpdoc/en/functions/pdf.xml diff -u phpdoc/en/functions/pdf.xml:1.50 phpdoc/en/functions/pdf.xml:1.51 --- phpdoc/en/functions/pdf.xml:1.50Sun May 20 20:28:10 2001 +++ phpdoc/en/functions/pdf.xml Sun May 20 20:36:19 2001 @@ -1990,12 +1990,12 @@ refsect1 titleDescription/title funcsynopsis - funcprototype - funcdefvoid functionpdf_setdash/function/funcdef - paramdefint parameterpdf object/parameter/paramdef - paramdefdouble parameterw/parameter/paramdef - paramdefdouble parameterb/parameter/paramdef - /funcprototype +funcprototype + funcdefvoid functionpdf_setdash/function/funcdef + paramdefint parameterpdf object/parameter/paramdef + paramdefdouble parameterb/parameter/paramdef + paramdefdouble parameterw/parameter/paramdef +/funcprototype /funcsynopsis para Set the current dash pattern to b black and w white units.
Re: [PHP-DOC] Function References not showing up in docs for mixed case function names
Actually, I think that having function names in anything but lower case only makes the manual less consistant and could even confuse new comers by possibly making them think that certain functions that are written a certain way in the docs (ala pdflib) must be written that way in code. I would propose that a phpdoc wide change be made so that all functions are written in lowercase form. It's not necessary to have them in a mixed case created on the author's whim. My 2 cents... Daniel - Original Message - From: [EMAIL PROTECTED] Newsgroups: php.doc To: [EMAIL PROTECTED] Sent: Saturday, May 19, 2001 5:10 PM Subject: Re: [PHP-DOC] Function References not showing up in docs for mixed case function names Linking is case sensitive. You should use lowercase names to have links. function-names are NOT case-sensitive in PHP itself... so why not change the stylesheets or something so that it is NOT case-sensitive in the docs either? We've got an excellent DSSSL-fu'er over here :), maybe he or someone else knows how to change that? Greetz, Jeroen
[PHP-DOC] cvs: phpdoc /en/functions com.xml
danbeck Fri May 18 09:33:08 2001 EDT Modified files: /phpdoc/en/functionscom.xml Log: corrected endtag on line 161... you should really run 'make test' before committing changes... Index: phpdoc/en/functions/com.xml diff -u phpdoc/en/functions/com.xml:1.12 phpdoc/en/functions/com.xml:1.13 --- phpdoc/en/functions/com.xml:1.12Fri May 18 08:04:09 2001 +++ phpdoc/en/functions/com.xml Fri May 18 09:33:07 2001 @@ -158,7 +158,7 @@ funcsynopsis funcprototype funcdefstring functionVARIANT::VARIANT/function/funcdef - paramdefmixed parameteroptionalvalue/optional/parameter/paramdef + paramdefmixed parameteroptionalvalue/optional/parameter/paramdef paramdefint parameteroptionaltype/optional/parameter/paramdef paramdefint parameteroptionalcodepage/optional/parameter/paramdef /funcprototype
[PHP-DOC] cvs: phpdoc /en/functions apache.xml
danbeck Fri May 18 13:47:10 2001 EDT Modified files: /phpdoc/en/functionsapache.xml Log: resorted functions in alpha-numeric order Index: phpdoc/en/functions/apache.xml diff -u phpdoc/en/functions/apache.xml:1.9 phpdoc/en/functions/apache.xml:1.10 --- phpdoc/en/functions/apache.xml:1.9 Wed May 16 11:33:20 2001 +++ phpdoc/en/functions/apache.xml Fri May 18 13:47:09 2001 @@ -87,6 +87,58 @@ /refsect1 /refentry + refentry id=function.ascii2ebcdic + refnamediv +refnameascii2ebcdic/refname +refpurposeTranslate string from ASCII to EBCDIC/refpurpose + /refnamediv + refsect1 +titleDescription/title +funcsynopsis + funcprototype + funcdefint functionascii2ebcdic/function/funcdef + paramdefstring parameterascii_str/parameter/paramdef + /funcprototype +/funcsynopsis +para + functionascii2ebcdic/function is an Apache-specific function which + is available only on EBCDIC based operating systems (OS/390, BS2000). + It translates the ASCII encoded string parameterascii_str/parameter + to its equivalent EBCDIC representation (binary safe), and returns + the result. +/para +para + See also the reverse function functionebcdic2ascii/function +/para + /refsect1 + /refentry + + refentry id=function.ebcdic2ascii + refnamediv +refnameebcdic2ascii/refname +refpurposeTranslate string from EBCDIC to ASCII/refpurpose + /refnamediv + refsect1 +titleDescription/title +funcsynopsis + funcprototype + funcdefint functionebcdic2ascii/function/funcdef + paramdefstring parameterebcdic_str/parameter/paramdef + /funcprototype +/funcsynopsis +para + functionebcdic2ascii/function is an Apache-specific function which + is available only on EBCDIC based operating systems (OS/390, BS2000). + It translates the EBCDIC encoded string parameterebcdic_str/parameter + to its equivalent ASCII representation (binary safe), and returns + the result. +/para +para + See also the reverse function functionascii2ebcdic/function +/para + /refsect1 + /refentry + refentry id=function.getallheaders refnamediv refnamegetallheaders/refname @@ -163,58 +215,6 @@ use functioninclude/function or functionrequire/function; functionvirtual/function cannot be used to include a document which is itself a PHP file. -/para - /refsect1 - /refentry - - refentry id=function.ascii2ebcdic - refnamediv -refnameascii2ebcdic/refname -refpurposeTranslate string from ASCII to EBCDIC/refpurpose - /refnamediv - refsect1 -titleDescription/title -funcsynopsis - funcprototype - funcdefint functionascii2ebcdic/function/funcdef - paramdefstring parameterascii_str/parameter/paramdef - /funcprototype -/funcsynopsis -para - functionascii2ebcdic/function is an Apache-specific function which - is available only on EBCDIC based operating systems (OS/390, BS2000). - It translates the ASCII encoded string parameterascii_str/parameter - to its equivalent EBCDIC representation (binary safe), and returns - the result. -/para -para - See also the reverse function functionebcdic2ascii/function -/para - /refsect1 - /refentry - - refentry id=function.ebcdic2ascii - refnamediv -refnameebcdic2ascii/refname -refpurposeTranslate string from EBCDIC to ASCII/refpurpose - /refnamediv - refsect1 -titleDescription/title -funcsynopsis - funcprototype - funcdefint functionebcdic2ascii/function/funcdef - paramdefstring parameterebcdic_str/parameter/paramdef - /funcprototype -/funcsynopsis -para - functionebcdic2ascii/function is an Apache-specific function which - is available only on EBCDIC based operating systems (OS/390, BS2000). - It translates the EBCDIC encoded string parameterebcdic_str/parameter - to its equivalent ASCII representation (binary safe), and returns - the result. -/para -para - See also the reverse function functionascii2ebcdic/function /para /refsect1 /refentry
[PHP-DOC] cvs: phpdoc / global.ent
danbeck Thu May 17 13:22:34 2001 EDT Modified files: /phpdoc global.ent Log: Added reference to PDFLib's Thomas Merz Index: phpdoc/global.ent diff -u phpdoc/global.ent:1.92 phpdoc/global.ent:1.93 --- phpdoc/global.ent:1.92 Thu May 17 05:38:17 2001 +++ phpdoc/global.ent Thu May 17 13:22:34 2001 @@ -1,6 +1,6 @@ !-- -*- SGML -*- - $Id: global.ent,v 1.92 2001/05/17 12:38:17 martin Exp $ + $Id: global.ent,v 1.93 2001/05/17 20:22:34 danbeck Exp $ Contains global macros for all the SGML documents. @@ -97,6 +97,7 @@ !ENTITY url.psgml ftp://ftp.lysator.liu.se/pub/sgml/psgml-1.0.1.tar.gz; !ENTITY url.pcre ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/; !ENTITY url.pdf http://www.pdflib.com/pdflib/index.html; +!ENTITY url.pdflib.merz http://www.pdflib.com/corporate/tm.html; !ENTITY url.pfpro http://www.verisign.com/payment/; !ENTITY url.pfpro.download https://testmanager.signio.com/Downloads/Downloads_secure.htm; !ENTITY url.php http://www.php.net/;
[PHP-DOC] cvs: phpdoc /en/chapters install.xml
danbeck Thu May 17 14:44:38 2001 EDT Modified files: /phpdoc/en/chapters install.xml Log: added info for pdflib configuration\nand updated pdflib version information\nin several places. Index: phpdoc/en/chapters/install.xml diff -u phpdoc/en/chapters/install.xml:1.59 phpdoc/en/chapters/install.xml:1.60 --- phpdoc/en/chapters/install.xml:1.59 Fri May 11 06:35:28 2001 +++ phpdoc/en/chapters/install.xml Thu May 17 14:44:38 2001 @@ -1339,7 +1339,7 @@ PHP 3: jpeg dir for pdflib 2.0 /para para - PHP 4: jpeg dir for pdflib 3.x + PHP 4: jpeg dir for pdflib 3.x and 4.x /para /listitem /varlistentry @@ -1352,7 +1352,7 @@ PHP 3: Option not available in PHP 3 /para para - PHP 4: png dir for pdflib 3.x + PHP 4: png dir for pdflib 3.x and 4.x /para /listitem /varlistentry @@ -1395,7 +1395,7 @@ PHP 3: tiff dir for pdflib 2.0 /para para - PHP 4: tiff dir for pdflib 3.x + PHP 4: tiff dir for pdflib 3.x and 4.x /para /listitem /varlistentry @@ -2076,9 +2076,24 @@ filename/usr/local/filename. /para para -PHP 4: Include pdflib 3.x support. DIR is the pdflib install -directory, which defaults to filename/usr/local/filename. +PHP 4: Include pdflib 3.x/4.x support. DIR is the pdflib install +location, which defaults to filename/usr/local/filename. /para + para + PHP 4 and PDFlib 3.x/4.x require that you have the JPEG and + TIFF libraries available. When compiling PDFlib support, use + the link + linkend=install.configure.with-jpeg-dir--with-jpeg-dir/link + and link + linkend=install.configure.with-tiff-dir--with-tiff-dir/link + configure options. You may wish to additionally specify the + link + linkend=install.configure.with-png-dir--with-png-dir/link + and link + linkend=install.configure.with-zlib-dir--with-zlib-dir/link + configure options to compile PNG and Zlib support into the + PDFlib extension. + /para /listitem /varlistentry @@ -2088,7 +2103,7 @@ /term listitem para -PHP 3, PHP 4: Activate pdflib as shared librairy. +PHP 3, PHP 4: Activate pdflib as shared library. /para /listitem /varlistentry @@ -2242,7 +2257,7 @@ PHP 3: zlib dir for pdflib 2.0 or include zlib support /para para -PHP 4: zlib dir for pdflib 3.x or include zlib support +PHP 4: zlib dir for pdflib 3.x/4.x or include zlib support /para /listitem /varlistentry
[PHP-DOC] cvs: phpdoc /en/functions pdf.xml
danbeck Thu May 17 14:49:51 2001 EDT Modified files: /phpdoc/en/functionspdf.xml Log: clarification of introductory text Index: phpdoc/en/functions/pdf.xml diff -u phpdoc/en/functions/pdf.xml:1.46 phpdoc/en/functions/pdf.xml:1.47 --- phpdoc/en/functions/pdf.xml:1.46Mon May 7 23:53:41 2001 +++ phpdoc/en/functions/pdf.xml Thu May 17 14:49:51 2001 @@ -6,59 +6,64 @@ sect1 id=pdf.intro titleIntroduction/title simpara - You can use the PDF functions in PHP to create PDF files if you - have the PDF library by Thomas Merz (available at - ulink url=url.pdf;url.pdf;/ulink; - you will also need ulink url=url.jpeg;the JPEG library/ulink - and ulink url=url.tiff;the TIFF library/ulink to - compile this. These two librariess can often cause problems when - configuring PHP, so be sure to pay attention to the output of - the configure script and fix any problems it reports. +The PDF functions in PHP can create PDF files using the PDFlib +library created by ulink url=url.pdflib.merz;Thomas +Merz/ulink. PDFlib is available at ulink +url=url.pdf;url.pdf;/ulink. The ulink +url=url.jpeg;JPEG/ulink and ulink +url=url.tiff;TIFF/ulink libraries are required to compile +this extension. Please see the link +linkend=install.configure.with-pdflibPDFlib installation/link +section for more information about compiling PDF support into PHP. /simpara simpara - Please consult the documentation for PDFlib shipped with + Please consult the documentation for PDFlib included with the source distribution of PDFlib. It provides a very good overview of what PDFlib is capable of doing and contains the full - and most up-to-date description of all functions. + and most up-to-date documentation of all functions. /simpara simpara - All of the functions in PDFlib and the PHP module have the same name. - The parameters are also identical. - You should also understand some of the concepts of PDF - or PostScript to efficiently use this module. - All lengths and coordinates are measured in PostScript points. - There are generally 72 PostScript points to an inch, but this - depends on the output resolution. -/simpara -simpara - There is another PHP module for PDF document creation based on - ulink url=url.cpdf;FastIO's/ulink. - ClibPDF. It has a slightly different API. Check the - link linkend=ref.cpdfClibPDF functions/link section for - details. -/simpara -simpara - The PDF module introduces one new type of variable. - It is called a parameterpdf object/parameter and - almost all functions need a parameterpdf object/parameter - as its first parameter. - /simpara + All of the functions in PDFlib and the PHP module have identical + function names and parameters. You will need to understand some + of the basic concepts of PDF and PostScript to efficiently use + this extension. All lengths and coordinates are measured in + PostScript points. There are generally 72 PostScript points to an + inch, but this depends on the output resolution. Please see the + PDFlib documentation included with the source distribution of + PDFlib for a more thorough explanation of the coordinate system + used. +/simpara + simpara +Please note that most of the PDF functions require a +parameterpdf object/parameter as it's first parameter. Please +see the examples below for more information. + /simpara + note +para + An alternative PHP module for PDF document creation based on + ulink url=url.cpdf;FastIO's/ulink ClibPDF is + available. Please see the link linkend=ref.cpdfClibPDF/link + section for details. Note that link + linkend=ref.cpdfClibPDF/link has a slightly different API + compared to PDFlib. +/para + /note /sect1 sect1 id=pdf.oldlibs.confusion -titleConfusion with old PDFlib versions/title -simpara - Starting with PHP 4.0.5, the PHP extension for PDFlib is officially - supported by PDFlib GmbH. This means that all the functions - described in the PDFlib-manual (V3.00 or greater) are supported by - PHP 4 with exactly the same meaning and the same parameters. - Only the return values may differ from the PDFlib manual, because - the PHP convention of returning literalfalse/literal was adopted. - For compatibility reasons this binding for - PDFlib still supports the old functions, but as stated above - they should be replaced by their new versions. PDFlib GmbH will not - support any problems arising from the use of these deprecated - functions. -/simpara +titleConfusion with old PDFlib versions/title + simpara +Starting with PHP 4.0.5, the PHP extension for PDFlib is +officially supported by PDFlib GmbH. This means that all the +
[PHP-DOC] cvs: phpdoc /en/functions pdf.xml
danbeck Thu May 17 15:40:32 2001 EDT
Modified files:
/phpdoc/en/functionspdf.xml
Log:
clarified analog clock description and reference to CLibPDF, fixed return type of
PDF_findfont, put PDF_open_memory_image in aphanumeric order and converted some of the
function names from pdf_ to PDF_
Index: phpdoc/en/functions/pdf.xml
diff -u phpdoc/en/functions/pdf.xml:1.47 phpdoc/en/functions/pdf.xml:1.48
--- phpdoc/en/functions/pdf.xml:1.47Thu May 17 14:49:51 2001
+++ phpdoc/en/functions/pdf.xml Thu May 17 15:40:32 2001
@@ -293,12 +293,11 @@
/para
para
The PDFlib distribution contains a more complex example which
- creates a page with an analog clock. Here we use
- the in memory creation feature of PDFlib, so we don't need
- any tmp-files. This example
- converted into PHP using PDFlib looks as the following (you
- can see the same example in the documentation for the
- link linkend=ref.cpdfclibpdf module)/link:
+ creates a page with an analog clock. Here we use the in memory
+ creation feature of PDFlib to alleviate the need to use temporary
+ files. The example, converted to PHP from the PDFlib example, is
+ as follows: (The same example is available in the link
+ linkend=ref.cpdfCLibPDF/link documentation.)
/para
para
example
@@ -536,7 +535,7 @@
refentry id=function.pdf-add-outline
refnamediv
-refnamepdf_add_outline/refname
+refnamePDF_add_outline/refname
refpurposeDeprecated: Adds bookmark for current page/refpurpose
/refnamediv
refsect1
@@ -1151,7 +1150,7 @@
titleDescription/title
funcsynopsis
funcprototype
- funcdefvoid functionPDF_findfont/function/funcdef
+ funcdefint functionPDF_findfont/function/funcdef
paramdefint parameterpdf object/parameter/paramdef
paramdefstring parameterfontname/parameter/paramdef
paramdefstring parameterencoding^/parameter/paramdef
@@ -1165,6 +1164,25 @@
macroman, winansi, host, or a user-defined encoding name,
or the name of a CMap.
/para
+ para
+functionPDF_findfont/function returns a font handle or false
+on error.
+ /para
+ para
+example
+ titlefunctionPDF_findfont/function example/title
+ programlisting role=php
+lt;php
+
+$font = pdf_findfont($pdf, Times New Roman, winansi, 1);
+if ($font) {
+pdf_setfont($pdf, $font, 10);
+}
+
+?gt;
+ /programlisting
+/example
+ /para
/refsect1
/refentry
@@ -1470,7 +1488,7 @@
refentry id=function.pdf-open
refnamediv
-refnamepdf_open/refname
+refnamePDF_open/refname
refpurposeDeprecated: Open a new pdf object/refpurpose
/refnamediv
refsect1
@@ -1656,6 +1674,47 @@
/refsect1
/refentry
+ refentry id=function.pdf-open-memory-image
+ refnamediv
+ refnamePDF_open_memory_image/refname
+ refpurposeOpens an image created with PHP's image functions/refpurpose
+ /refnamediv
+ refsect1
+ titleDescription/title
+ funcsynopsis
+funcprototype
+ funcdefint functionPDF_open_memory_image/function/funcdef
+ paramdefint parameterpdf object/parameter/paramdef
+ paramdefint parameterimage/parameter/paramdef
+/funcprototype
+ /funcsynopsis
+ para
+The functionPDF_open_memory_image/function function takes
+an image created with the PHP's image functions and makes it available
+for the pdf object. The function returns a pdf
+image identifier.
+
+example
+ titleIncluding a memory image/title
+ programlisting
+lt;?php
+$im = ImageCreate(100, 100);
+$col = ImageColorAllocate($im, 80, 45, 190);
+ImageFill($im, 10, 10, $col);
+$pim = PDF_open_memory_image($pdf, $im);
+ImageDestroy($im);
+PDF_place_image($pdf, $pim, 100, 100, 1);
+PDF_close_image($pdf, $pim);
+?
+ /programlisting
+/example/para
+ para
+See also functionPDF_close_image/function,
+functionPDF_place_image/function./para
+ /refsect1
+ /refentry
+
+
refentry id=function.pdf-open-pdi
refnamediv
refnamePDF_open_pdi/refname
@@ -1963,28 +2022,31 @@
/refsect1
/refentry
- refentry id=function.pdf-setfont
- refnamediv
-refnamePDF_setfont/refname
-refpurposeSet the current font/refpurpose
- /refnamediv
- refsect1
-titleDescription/title
-funcsynopsis
- funcprototype
- funcdefvoid functionPDF_setfont/function/funcdef
- paramdefint parameterpdf object/parameter/paramdef
- paramdefint parameterfont/parameter/paramdef
- paramdefdouble parametersize/parameter/paramdef
- /funcprototype
-/funcsynopsis
-para
- Set the current font in the given size, using a
- parameterfont/parameter handle returned by
- functionPDF_findfont/function
-/para
- /refsect1
- /refentry
+ refentry id=function.pdf-setfont
+ refnamediv
+ refnamePDF_setfont/refname
+ refpurposeSet the current font/refpurpose
+ /refnamediv
+ refsect1
+
Re: [PHP-DOC] cvs: phpdoc /en/language oop.xml
I'll correct those two functions for you tonight. Daniel - Original Message - From: Kristian Köhntopp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 17, 2001 6:05 PM Subject: [PHP-DOC] cvs: phpdoc /en/language oop.xml kk Thu May 17 16:05:01 2001 EDT Modified files: /phpdoc/en/language oop.xml Log: - Extended documentation for object orientation. This should now cover most, if not all features of PHP 4 object orientation, reflecting the greatly improved OO features in PHP 4. - The documentation for serialize() and unserialize() is still stating that class associations are lost. This is no longer true in PHP 4 and should be corrected. It is now 1am here. I am not going to fix that now, someone else should.
Re: [PHP-DOC] cvs: phpdoc /en/language oop.xml
It looks like you might have truncated this sentence in the language.oop.serialization section of oop.xml: caution simpara The following information is valid for PHP4 only. In PHP3, an /simpara /caution Daniel - Original Message - From: Kristian Köhntopp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 17, 2001 6:05 PM Subject: [PHP-DOC] cvs: phpdoc /en/language oop.xml kk Thu May 17 16:05:01 2001 EDT Modified files: /phpdoc/en/language oop.xml Log: - Extended documentation for object orientation. This should now cover most, if not all features of PHP 4 object orientation, reflecting the greatly improved OO features in PHP 4. - The documentation for serialize() and unserialize() is still stating that class associations are lost. This is no longer true in PHP 4 and should be corrected. It is now 1am here. I am not going to fix that now, someone else should.
[PHP-DOC] cvs: phpdoc /en/functions var.xml
danbeck Thu May 17 19:23:43 2001 EDT Modified files: /phpdoc/en/functionsvar.xml Log: added notes about serializing objects in php4 and added links to the new serialization section of oop.xml Index: phpdoc/en/functions/var.xml diff -u phpdoc/en/functions/var.xml:1.47 phpdoc/en/functions/var.xml:1.48 --- phpdoc/en/functions/var.xml:1.47Thu May 17 01:03:33 2001 +++ phpdoc/en/functions/var.xml Thu May 17 19:23:42 2001 @@ -883,14 +883,23 @@ This is useful for storing or passing PHP values around without losing their type and structure. /simpara -simpara - To make the serialized string into a PHP value again, use - functionunserialize/function.functionSerialize/function - handles the types typeinteger/type, typedouble/type, - typestring/type, typearray/type (multidimensional) and - typeobject/type (object properties will be serialized, but - methods are lost). -/simpara + simpara +To make the serialized string into a PHP value again, use +functionunserialize/function. functionSerialize/function +handles the types typeinteger/type, typedouble/type, +typestring/type, typearray/type (multidimensional) and +typeobject/type. + /simpara + note +para + In PHP 3, object properties will be serialized, but methods are + lost. PHP 4 removes that limitation and restores both properties + and methods. Please see the link + linkend=language.oop.serializationSerializing Objects/link + section of link linkend=language.oopClasses and + Objects/link for more information. +/para + /note para example titlefunctionSerialize/function example/title @@ -913,6 +922,9 @@ /programlisting /example /para + para +See Also: functionunserialize/function. + /para /refsect1 /refentry @@ -1019,6 +1031,16 @@ If an object was serialized, its methods are not preserved in the returned value. /simpara + note +para + In PHP 3, methods are not preserved when unserializing a + serialized object. PHP 4 removes that limitation and restores + both properties and methods. Please see the link + linkend=language.oop.serializationSerializing Objects/link + section of link linkend=language.oopClasses and + Objects/link or more information. +/para + /note para example titlefunctionUnserialize/function example/title @@ -1044,6 +1066,9 @@ /programlisting /example /para + para +See Also: functionserialize/function. + /para /refsect1 /refentry
Re: [PHP-DOC] cvs: phpdoc /ja/functions array.xml datetime.xml ming.xml openssl.xml pspell.xml
What is emanual.exe? It's show up on several emails from jessica now... Daniel - Original Message - From: jessica [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, April 23, 2001 9:08 AM Subject: [PHP-DOC] cvs: phpdoc /ja/functions array.xml datetime.xml ming.xml openssl.xml pspell.xml hirokawa Sun Apr 8 16:07:42 2001 EDT Modified files: /phpdoc/ja/functions array.xml datetime.xml ming.xml openssl.xml pspell.xml Log: fixing typos, update translation.
Re: [PHP-DOC] php redirect
Please do not post general help questions to the PHP documentation list.
This list is primarly for discussing PHP documentation additions,
corrections or anything else pertaining to writing PHP documentation. You
probably want to unsubscribe from this list and then subscribe yourself to
the PHP General User List. You can do both of these things at:
http://www.php.net/support.php.
But, to answer your question, you need to use the header() function to send
a "Location" header to the browser. You can find documentation about the
header() function at http://php.net/header/.
e.g.
?
header("Location: http://www.php.net/");
?
Regards,
Daniel Beckham
- Original Message -
From: "Arthur Melkonyan" [EMAIL PROTECTED]
Newsgroups: php.doc,php.windows
To: [EMAIL PROTECTED]
Sent: Saturday, April 21, 2001 4:34 PM
Subject: [PHP-DOC] php redirect
I'm trying to do redirect but couldn't fined any materials about
redirect
Any one knows how to do in php.
Re: [PHP-DOC] Could somebody pls. correct a typo?
If he said br/, then his entire argument makes no sense. The nl2br() function returns br /, not br/. I'm not sure what he's having difficulty with. =) I think that I just assumed that by saying br/ he actually meant br /. Daniel - Original Message - From: "Hojtsy Gabor" [EMAIL PROTECTED] To: "Daniel Beckham" [EMAIL PROTECTED] Sent: Saturday, April 21, 2001 5:13 AM Subject: Re: [PHP-DOC] Could somebody pls. correct a typo? No, it's not difficult, but why should it really matter? br / or p / or hr /, et. al. should all be compatible with older browsers. Like I said, it's perfectly valid SGML/XML. The following html works flawlessly in NS 4.72: html headtitle/title/head body This is a test. p / This is another test.br /br /br / This is a final test. hr / /body /html Original text by Thomas: | since Browsers like Netscape 4.x don't react on br/ He said br/ not br / the first wont work (see the XHTML spec). Goba ... . . . . . Editor of the Hungarian PHP manual, Admin of the Hungarian PHP mirror
Re: [PHP-DOC] Could somebody pls. correct a typo?
Are you positive that Netscape 4.x will not see a br / as a line break? This is perfectly formed sgml or xml as far as I know. Daniel - Original Message - From: "Thomas" [EMAIL PROTECTED] Newsgroups: php.doc To: [EMAIL PROTECTED] Sent: Thursday, April 19, 2001 5:05 PM Subject: Re: [PHP-DOC] Could somebody pls. correct a typo? But shouldn't that be worth a short comment in the doc (like "inserts XHTML breaks..." instead of "HTML breaks", and when the change (from what) happened?) , since Browsers like Netscape 4.x don't react on br/? Or have I missed a section with all these things one has to consider (know) before - or at least after upgrading - (like $array[myfield] and the backward-compatible nl2br "doesn't work anymore")?
Re: [PHP-DOC] Could somebody pls. correct a typo?
Don't know about version 4.0.4, but I'm testing 4.0.5-dev now and it's outputting br /. Daniel - Original Message - From: "Damien Seguy" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, April 20, 2001 2:23 AM Subject: Re: [PHP-DOC] Could somebody pls. correct a typo? Hi, - would somebody pls. correct br/ to br in both lagunages? That's not a typo. nl2br() uses XHTML br / tags since PHP-4.0.4 Thats the correct syntax nowadays. Are you sure of this? I just tested it on a 4.0.4pl1 version, and it still gives me br. Or this may be browser dependent? Or am I missing something? Best regards, Damien Seguy
Re: [PHP-DOC] Could somebody pls. correct a typo?
No, it's not difficult, but why should it really matter? br / or p / or hr /, et. al. should all be compatible with older browsers. Like I said, it's perfectly valid SGML/XML. The following html works flawlessly in NS 4.72: html headtitle/title/head body This is a test. p / This is another test.br /br /br / This is a final test. hr / /body /html Regards, Daniel Beckham - Original Message - From: "Thomas" [EMAIL PROTECTED] Newsgroups: php.doc To: [EMAIL PROTECTED] Sent: Friday, April 20, 2001 3:32 AM Subject: Re: [PHP-DOC] Could somebody pls. correct a typo? What I meant: Shouldn't HTML be changed to XHTML? And is it really that bad to write also a note like "Note: In versions older than PHP 4.04 nl2br() returned a string with 'br' inserted before all newlines." ? For behavior-changes like this: Please have in mind, that there are millions scripts running out there, and not all of them running on the last PHP-version. Is there a consideration for eventually occuring "traps" for the change to 4.05? I assume that it's not really funny if a user - or worse - ISP upgrades, and than can't defend against complaints because of "buggy" scripts (which worked before). Anil Madhavapeddy wrote: - would somebody pls. correct br/ to br in both lagunages? That's not a typo. nl2br() uses XHTML br / tags since PHP-4.0.4 Thats the correct syntax nowadays. Agreed. Regards, Thomas
[PHP-DOC] cvs: phpdoc /en/functions imap.xml
danbeck Tue Apr 10 08:42:24 2001 EDT Modified files: /phpdoc/en/functionsimap.xml Log: added see also notes to imap_num_msg and imap_num_recent Index: phpdoc/en/functions/imap.xml diff -u phpdoc/en/functions/imap.xml:1.33 phpdoc/en/functions/imap.xml:1.34 --- phpdoc/en/functions/imap.xml:1.33 Thu Apr 5 17:14:54 2001 +++ phpdoc/en/functions/imap.xmlTue Apr 10 08:42:24 2001 @@ -1844,6 +1844,10 @@ para Return the number of messages in the current mailbox. /para +para + See also: functionimap_num_recent/function and + functionimap_status/function. +/para /refsect1 /refentry @@ -1863,6 +1867,10 @@ /funcsynopsis para Returns the number of recent messages in the current mailbox. +/para +para + See also: functionimap_num_msg/function and + functionimap_status/function. /para /refsect1 /refentry
Re: [PHP-DOC] php.net manual status
Sorry.. I was looking for some changes that I made last Thursday afternoon. They haven't shown up yet. This page: http://www.php.net/manual/en/ref.imap.php does not seem to reflect what is in en/functions/imap.xml currently in cvs. Daniel - Original Message - From: "Egon Schmid (@work)" [EMAIL PROTECTED] To: "Daniel Beckham" [EMAIL PROTECTED] Cc: "phpdoc" [EMAIL PROTECTED] Sent: Monday, April 09, 2001 11:48 AM Subject: Re: [PHP-DOC] php.net manual status Daniel Beckham wrote: Anyone know what the status of the online manual at php.net is? It hasn't been updated in some time... Last updated: Sun, 08 Apr 2001. Please have a look in the upper right corner. -Egon -- SIX Offene Systeme GmbH Stuttgart - Berlin Sielminger Strae 63 D-70771 Leinfelden-Echterdingen Fon +49 711 9909164 Fax +49 711 9909199 http://www.six.de
[PHP-DOC] cvs: phpdoc /en/language control-structures.xml
danbeck Mon Apr 9 14:50:14 2001 EDT
Modified files:
/phpdoc/en/language control-structures.xml
Log:
notes and examples added to foreach
Index: phpdoc/en/language/control-structures.xml
diff -u phpdoc/en/language/control-structures.xml:1.27
phpdoc/en/language/control-structures.xml:1.28
--- phpdoc/en/language/control-structures.xml:1.27 Mon Apr 9 12:15:45 2001
+++ phpdoc/en/language/control-structures.xml Mon Apr 9 14:50:14 2001
@@ -461,23 +461,31 @@
para
note
para
- When literalforeach/literal first starts executing, the
+ When literalforeach/literal first starts executing, the
internal array pointer is automatically reset to the first element
of the array. This means that you do not need to call
functionreset/function before a literalforeach/literal
loop.
-/para
- /note
+ /para
+/note
/para
para
note
-para
- Also note that literalforeach/literal operates on a copy of
- the specified array, not the array itself, therefore the array
- pointer is not modified like with the each construct.
-/para
+ para
+ Also note that literalforeach/literal operates on a copy of
+ the specified array, not the array itself, therefore the array
+ pointer is not modified as with the functioneach/function
+ construct and changes to the array element returned are not
+ reflected in the original array.
+ /para
/note
/para
+ note
+para
+ literalforeach/literal does not support the ability to
+ suppress error messages using '@'.
+/para
+ /note
para
You may have noticed that the following are functionally
identical:
@@ -540,6 +548,25 @@
foreach($a as $k =gt; $v) {
print "\$a[$k] =gt; $v.\n";
+}
+
+/* foreach example 4: multi-dimensional arrays */
+
+$a[0][0] = "a";
+$a[0][1] = "b";
+$a[1][0] = "y";
+$a[1][1] = "z";
+
+foreach($a as $v1) {
+foreach ($v1 as $v2) {
+print "$v2\n";
+}
+}
+
+/* foreach example 5: dynamic arrays
+
+foreach(array(1, 2, 3, 4, 5) as $v) {
+print "$v\n";
}
/programlisting
/informalexample
[PHP-DOC] cvs: phpdoc /en/functions datetime.xml
danbeck Fri Apr 6 22:30:19 2001 EDT
Modified files:
/phpdoc/en/functionsdatetime.xml
Log:
corrected doc bug #9988
Index: phpdoc/en/functions/datetime.xml
diff -u phpdoc/en/functions/datetime.xml:1.35 phpdoc/en/functions/datetime.xml:1.36
--- phpdoc/en/functions/datetime.xml:1.35 Mon Mar 19 16:57:21 2001
+++ phpdoc/en/functions/datetime.xmlFri Apr 6 22:30:19 2001
@@ -271,7 +271,7 @@
$today = date("Ymd"); // 20010310
$today = date('h-i-s, j-m-y, it is w Day z '); // 05-16-17, 10-03-01, 1631 1618 6
Fripm01
$today = date('\i\t \i\s \t\h\e jS \d\a\y.'); // It is the 10th day.
-$today = date("D M j g:i:s T Y"); // Sat Mar 10 15:16:08 MST 2001
+$today = date("D M j G:i:s T Y"); // Sat Mar 10 15:16:08 MST 2001
$today = date('H:m:s \m \i\s\ \m\o\n\t\h'); // 17:03:17 m is month
$today = date("H:i:s"); // 17:16:17
/programlisting
[PHP-DOC] cvs: phpdoc /en/functions filesystem.xml
danbeck Mon Apr 2 09:43:28 2001 EDT
Modified files:
/phpdoc/en/functionsfilesystem.xml
Log:
added docs for pathinfo
Index: phpdoc/en/functions/filesystem.xml
diff -u phpdoc/en/functions/filesystem.xml:1.60 phpdoc/en/functions/filesystem.xml:1.61
--- phpdoc/en/functions/filesystem.xml:1.60 Mon Mar 26 15:50:26 2001
+++ phpdoc/en/functions/filesystem.xml Mon Apr 2 09:43:28 2001
@@ -2100,6 +2100,61 @@
/refsect1
/refentry
+
+ refentry id="function.pathinfo"
+ refnamediv
+refnamepathinfo/refname
+refpurposeReturns information about a file path/refpurpose
+ /refnamediv
+ refsect1
+titleDescription/title
+funcsynopsis
+ funcprototype
+ funcdefarray functionpathinfo/function/funcdef
+ paramdefstring parameterpath/parameter/paramdef
+ /funcprototype
+/funcsynopsis
+para
+ functionpathinfo/function returns an associative array
+ containing information about parameterpath/parameter. The
+ following array elements are returned:
+ parameterdirname/parameter, parameterbasename/parameter
+ and parameterextension/parameter.
+/para
+para
+ example
+ titlefunctionpathinfo/function Example/title
+ programlisting role="php"
+lt;?php
+
+$path_parts = pathinfo("/www/htdocs/index.html");
+
+echo $path_parts["dirname"] . "\n";
+echo $path_parts["basename"] . "\n";
+echo $path_parts["extension"] . "\n";
+
+?gt;
+ /programlisting
+ /example
+/para
+para
+ Would produce:
+ informalexample
+ programlisting
+/www/htdocs
+index.html
+html
+ /programlisting
+ /informalexample
+/para
+para
+ See also functiondirname/function,
+ functionbasename/function and functionrealpath/function.
+/para
+ /refsect1
+ /refentry
+
+
refentry id="function.pclose"
refnamediv
refnamepclose/refname
[PHP-DOC] IMAP docs - function order
I just noticed something.. is there a reason that the imap docs are not sorted by alphanumeric order. Actually, I don't really see any rhyme or reason to the list as it's currently arranged. If no one objects, I might go ahead and resort these. Daniel
[PHP-DOC] cvs: phpdoc /en/functions classobj.xml
danbeck Tue Mar 27 08:07:03 2001 EDT Modified files: /phpdoc/en/functionsclassobj.xml Log: added note to help clarify return type of get_class Index: phpdoc/en/functions/classobj.xml diff -u phpdoc/en/functions/classobj.xml:1.14 phpdoc/en/functions/classobj.xml:1.15 --- phpdoc/en/functions/classobj.xml:1.14 Fri Mar 9 07:33:03 2001 +++ phpdoc/en/functions/classobj.xmlTue Mar 27 08:07:03 2001 @@ -315,6 +315,12 @@ This function returns the name of the class of which the object parameterobj/parameter is an instance. /para +note + para + functionget_class/function returns the class name in + lowercase form. + /para +/note simpara See also functionget_parent_class/function, functionis_subclass_of/function
[PHP-DOC] Generating a single section of docs at a time...
I know I'm dreaming, but is it possible to only generate a single section of the docs at a time when testing changes etc? Sometimes I feel the need to actually see what the changes I made look like before I commit them, but it takes a very long time to "make html" on my little dev box. I poked around the make file, but didn't see any way to do this automagically. Any ideas? Thanks, Daniel Beckham
Re: [PHP-DOC] Generating a single section of docs at a time...
Didn't think about that... thanks! Daniel - Original Message - From: "Egon Schmid (@work)" [EMAIL PROTECTED] To: "Daniel Beckham" [EMAIL PROTECTED] Cc: "phpdoc" [EMAIL PROTECTED] Sent: Tuesday, March 27, 2001 10:39 AM Subject: Re: [PHP-DOC] Generating a single section of docs at a time... Daniel Beckham wrote: I know I'm dreaming, but is it possible to only generate a single section of the docs at a time when testing changes etc? Sometimes I feel the need to actually see what the changes I made look like before I commit them, but it takes a very long time to "make html" on my little dev box. I poked around the make file, but didn't see any way to do this automagically. Any ideas? Edit manual.xml just before the final make. -Egon -- SIX Offene Systeme GmbH Stuttgart - Berlin Sielminger Strae 63 D-70771 Leinfelden-Echterdingen Fon +49 711 9909164 Fax +49 711 9909199 http://www.six.de Besuchen Sie uns auf der CeBIT 2001, Halle 6, Stand F62/4
Re: [PHP-DOC] cvs: phpdoc /en/functions classobj.xml
Cool, can this be used with get_class_vars() also? If not, it would be a logical change to go along with get_class_methods(). Thanks, Daniel - Original Message - From: "Andrei Zmievski" [EMAIL PROTECTED] To: "Daniel Beckham" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, March 27, 2001 11:42 AM Subject: Re: [PHP-DOC] cvs: phpdoc /en/functions classobj.xml On Tue, 27 Mar 2001, Daniel Beckham wrote: +$my_class = new myclass(); + +$class_methods = get_class_methods(get_class($my_class)); Since yesterday, you can also do get_class_methods($my_class) directly. -Andrei "The human brain is a wonderful thing. It starts working the moment you are born, and never stops until you stand up to speak in public. " -- Sir George Jessel
[PHP-DOC] cvs: phpdoc /en/functions classobj.xml
danbeck Tue Mar 27 13:56:07 2001 EDT Modified files: /phpdoc/en/functionsclassobj.xml Log: changed the version number of get_class_methods note Index: phpdoc/en/functions/classobj.xml diff -u phpdoc/en/functions/classobj.xml:1.18 phpdoc/en/functions/classobj.xml:1.19 --- phpdoc/en/functions/classobj.xml:1.18 Tue Mar 27 10:09:42 2001 +++ phpdoc/en/functions/classobj.xmlTue Mar 27 13:56:06 2001 @@ -347,7 +347,7 @@ /para note para - As of PHP 4.0.5, you can specify the object itself instead of + As of PHP 4.0.6, you can specify the object itself instead of parameterclass_name/parameter. For example: informalexample programlisting
Re: [PHP-DOC] missing aliases functions
Actually, I think it might be better to completely remove all references to aliases. People don't need to use them and they are only there to keep old code from breaking. The less people know about them, the better really. If we still need some sort of compatibility list, we could always create an alias/compatibility appendix and list all alias functions there. That way, they would at least be accessible to people who are reading or converting very old code. Daniel - Original Message - From: "Damien Seguy" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 14, 2001 2:39 AM Subject: [PHP-DOC] missing aliases functions Hi, This might a question for those of you who are on this list since a year or so... According to Zend's site (http://www.zend.com/phpfunc/nodoku_alias.php), there is a bunch of undocumented functions which are only aliases. Docs says that, for instance, mysql() is still available for downward compatibility, but there is no entry for mysql() function. Is this done on any purpose? I suggest adding those functions, in order to give entry on the manual, and explicitely write those functions are obsolets. If this sounds fine to you, I'll do it. Best regards, Damien Seguy. Here is a list of function I'm talking about. mysql-mysql_db_query mysql_createdb-mysql_create_db mysql_dbname-mysql_result mysql_dropdb-mysql_drop_db mysql_fieldflags-mysql_field_flags mysql_fieldlen-mysql_field_len mysql_fieldname-mysql_field_name mysql_fieldtable-mysql_field_table mysql_fieldtype-mysql_field_type mysql_freeresult-mysql_free_result mysql_listdbs-mysql_list_dbs mysql_listfields-mysql_list_fields mysql_listtables-mysql_list_tables mysql_numfields-mysql_num_fields mysql_numrows-mysql_num_rows mysql_selectdb-mysql_select_db pg_clientencoding-pg_client_encoding pg_setclientencoding-pg_set_client_encoding magic_quotes_runtime-set_magic_quotes_runtime
Re: [PHP-DOC] missing aliases functions
Sounds good to mean, what does everyone else think about this? - Original Message - From: "Damien Seguy" [EMAIL PROTECTED] To: "phpdoc" [EMAIL PROTECTED] Sent: Wednesday, March 14, 2001 10:10 AM Subject: Re: [PHP-DOC] missing aliases functions From Daniel : If we still need some sort of compatibility list, we could always create an alias/compatibility appendix and list all alias functions there. That way, they would at least be accessible to people who are reading or converting very old code. This seems reasonnable to me. We can call it "obsolete function", or "near extinction aliases", to insist on their nearing death. This appendix may give a chance to redirect people on modern entries.
[PHP-DOC] cvs: phpdoc /en/functions misc.xml
danbeck Thu Mar 8 11:47:24 2001 EDT
Modified files:
/phpdoc/en/functionsmisc.xml
Log:
added docs for the new constant function
Index: phpdoc/en/functions/misc.xml
diff -u phpdoc/en/functions/misc.xml:1.37 phpdoc/en/functions/misc.xml:1.38
--- phpdoc/en/functions/misc.xml:1.37 Thu Mar 8 09:57:13 2001
+++ phpdoc/en/functions/misc.xmlThu Mar 8 11:47:23 2001
@@ -75,6 +75,52 @@
/refsect1
/refentry
+ refentry id="function.constant"
+ refnamediv
+refnameconstant/refname
+refpurposeReturns the value of a constant/refpurpose
+ /refnamediv
+ refsect1
+titleDescription/title
+funcsynopsis
+ funcprototype
+ funcdefmixed functionconstant/function/funcdef
+ paramdefstring parametername/parameter/paramdef
+ /funcprototype
+/funcsynopsis
+simpara
+ functionconstant/function will return the value of the
+ constant indicated by parametername/parameter.
+/simpara
+simpara
+ functionconstant/function is useful if you need to retrieve
+ the value of a constant, but do not know it's name. i.e. It is
+ stored in a variable or returned by a function.
+/simpara
+para
+ example
+ titlefunctionconstant/function example/title
+ programlisting role="php"
+lt;php
+
+define ("MAXSIZE", 100);
+
+echo MAXSIZE;
+echo constant("MAXSIZE"); // same thing as the previous line
+
+?gt;
+ /programlisting
+ /example
+/para
+para
+ See also functiondefine/function,
+ functiondefined/function and the section on link
+ linkend="language.constants"Constants/link.
+/para
+ /refsect1
+ /refentry
+
+
refentry id="function.define"
refnamediv
refnamedefine/refname
@@ -147,7 +193,8 @@
an error occurs.
/para
para
- See also functiondefined/function and the section on link
+ See also functiondefined/function,
+ functionconstant/function and the section on link
linkend="language.constants"Constants/link.
/para
/refsect1
@@ -183,7 +230,8 @@
/example
/para
para
- See also functiondefine/function and the section on link
+ See also functiondefine/function,
+ functionconstant/function and the section on link
linkend="language.constants"Constants/link.
/para
/refsect1
[PHP-DOC] cvs: phpdoc /en/functions mysql.xml
danbeck Thu Mar 8 13:56:37 2001 EDT
Modified files:
/phpdoc/en/functionsmysql.xml
Log:
added errata clarification and clean up some function examples
Index: phpdoc/en/functions/mysql.xml
diff -u phpdoc/en/functions/mysql.xml:1.36 phpdoc/en/functions/mysql.xml:1.37
--- phpdoc/en/functions/mysql.xml:1.36 Thu Feb 15 16:15:33 2001
+++ phpdoc/en/functions/mysql.xml Thu Mar 8 13:56:37 2001
@@ -46,10 +46,11 @@
/funcprototype
/funcsynopsis
para
- functionmysql_affected_rows/function returns the number of
- rows affected by the last INSERT, UPDATE or DELETE query on the
- server associated with the specified link identifier. If the
- link identifier isn't specified, the last opened link is assumed.
+ functionmysql_affected_rows/function returns the number
+ of rows affected by the last INSERT, UPDATE or DELETE query
+ associated with parameterlink_identifier/parameter. If the
+ link identifier isn't specified, the last link opened by
+ functionmysql_connect/function is assumed.
/para
note
para
@@ -63,14 +64,27 @@
of the records will have been deleted from the table but this
function will return zero.
/para
+note
+ para
+ When using UPDATE, MySQL will not update columns where the new
+ value is the same as the old value. This creates the possiblity
+ that functionmysql_affected_rows/function may not actually
+ equal the number of rows matched, only the number of rows that
+ were literally affected by the query.
+ /para
+/note
para
- This command is not effective for SELECT statements, only on
- statements which modify records. To retrieve the number of rows
- returned from a SELECT, use functionmysql_num_rows/function.
+ functionmysql_affected_rows/function does not work with
+ SELECT statements; only on statements which modify records. To
+ retrieve the number of rows returned by a SELECT, use
+ functionmysql_num_rows/function.
/para
para
If the last query failed, this function will return -1.
/para
+para
+ See also: functionmysql_num_rows/function.
+/para
/refsect1
/refentry
@@ -242,11 +256,13 @@
titleMySQL connect example/title
programlisting role="php"
lt;?php
-$link = mysql_connect ("kraemer", "marliesle", "secret")
+
+$link = mysql_connect ("localhost", "username", "secret")
or die ("Could not connect");
print ("Connected successfully");
mysql_close ($link);
-?
+
+?gt;
/programlisting
/example
para See also
@@ -1533,29 +1549,30 @@
functionmysql_num_rows/function returns the number of rows in
a result set. This command is only valid for SELECT statements.
To retrieve the number of rows returned from a INSERT, UPDATE or
- DELETE, use functionmysql_affected_rows/function.
+ DELETE query, use functionmysql_affected_rows/function.
example
- title
- function
-mysql_num_rows example by [EMAIL PROTECTED]
- /function
- /title
+ titlefunctionmysql_num_rows/function example/title
programlisting role="php"
lt;?php
-$conn = mysql_connect("hostaddress", "username", "password");
-mysql_select_db("database",$conn); // needed if you have m,ultiple db's
-$Resultfornummembers = mysql_query("SELECT * FROM Accounts",$conn);
-$NumMembers = mysql_num_rows($Resultfornummembers);
-echo "$NumMembers Members";
-?
+
+$link = mysql_connect("localhost", "username", "password");
+mysql_select_db("database", $link);
+
+$result = mysql_query("SELECT * FROM table1", $link);
+$num_rows = mysql_num_rows($result);
+
+echo "$num_rows Rows\n";
+
+?gt;
/programlisting
/example
/para
para
See also:
- functionmysql_db_query/function,
- functionmysql_query/function and,
- functionmysql_fetch_row/function.
+ functionmysql_affected_rows/function,
+ functionmysql_connect/function,
+ functionmysql_select_db/function and
+ functionmysql_query/function.
/para
para
For downward compatibility functionmysql_numrows/function can
Re: [PHP-DOC] PHP reserved words
I think it's a great idea. Most language docs have a list of reserved words just as a routine thing... Daniel - Original Message - From: "Damien Seguy" [EMAIL PROTECTED] To: "phpdoc" [EMAIL PROTECTED] Sent: Tuesday, February 27, 2001 6:08 AM Subject: [PHP-DOC] PHP reserved words Hi I've compiled a list of PHP reserved words, and I'd like to commit it on the CVS tree. This is NOT the function list, but all those words used in PHP syntax, such as "for", "foreach", "return" and "class"..etc (zum Beispiel). All those notion are dispatched in differents files, and it is good to have them gathered. I made it an appendix. Any opinion? Best regards, Damien Seguy http://www.nexen.net/ l'hebergement dynamique ! Docs PHP/MySQL en Francais, scripts
Re: [PHP-DOC] Missing configure option in install.xml
Please do add these if you can... The en/chapters directory has been inaccessible for some time now. I have the --with-bz2 stuff already in my copy of install.xml, but I can not commit the change due to cvs server issues. Any idea when this stuff might be fixed guys? Daniel - Original Message - From: "Damien Seguy" [EMAIL PROTECTED] To: "phpdoc" [EMAIL PROTECTED] Sent: Friday, February 23, 2001 3:46 AM Subject: [PHP-DOC] Missing configure option in install.xml Hi , I went throw the doc, and I've pined down all those configure option which are in their own file, and not listed in install.xml. Here is a list of undefined tags, with the corresponding xml file. --with-bz2 (bz2.xml) --with-gmp (gmp.xml) --with-mnogosearch (mnogosearch.xml) --with-ovrimos (ovrimos.xml) --enable-shared-pdflib (pdfflib.xml) --with-recode (recode.xml) --enable-shmop (shmop.xml) --enable-wddx (wddx.xml) --enable-asp-tags (basic-syntax.xml) --enable-short-tags (basic-syntax.xml) As I review the doc, it seems that the description of --with-informix is wrong. If everyone's ok, I'll add all those options in the install.xml file. BTW, most options use the option tag, while some use the link tag, which usually link to the install.xml file, and is pretty much clever. I suggest using the link tag instead of option. Any opinions? best regards, Damien Seguy
