Re: [PHP-DOC] License change? Bye bye OPL, hello CC?
hi, late in the game, but a big +1 from me. Friedhelm Georg Richter wrote: Mehdi Achour schrieb: +1 for me! /Georg Fine with me. Mehdi On Tue, Jul 8, 2008 at 8:35 PM, Nuno Lopes [EMAIL PROTECTED] wrote: I'm fine with this license change as well. But please include the full license text in the appendix, just in case.. Nuno Hola, I too am for an open yet fair license. Awhile ago I wrote the following (and it appears I never followed up on it there!): http://news.php.net/php.doc.license/176 It lists three possible candidates with the one Hannes posted here as one of them. I do like this CC license because it's common, understandable, short, and has a pretty website :) If we voted this second I'd vote for it. However, I'm unclear how our required manner specified for attribution would be. I guess a link, and a certain phrase kinda like The Official PHP Manual or fancier words... Regards, Philip
Re: [PHP-DOC] Re: Notes Status, 20009 total
Hi Edward, Edward Z. Yang wrote: phpdoc@lists.php.net wrote: Following are the top 20 pages of the manual, sorted by the number of user notes contributed. These sections could use a polish, those notes represent 7.7% of the 20009 total user notes. 2 notes! I don't know if we should be celebrating or fearing this milestone. :-) Perhaps we should introduce a monthly Notes cleaning day ? ;-) Seriously, the figures suggests, we should improve some docs, mainly the cluttered session docs. Friedhelm p.s.: not very active the last years, but that could change
Re: [PHP-DOC] cvs: phpdoc /en/reference/bcompiler reference.xml /en/reference/dbplus reference.xml /en/reference/haru reference.xml /en/reference/ming reference.xml /en/reference/ncurses reference
Hi Philip, Philip Olson wrote: philip Thu Jun 14 02:34:50 2007 UTC Modified files: [...] /phpdoc/en/reference/ps reference.xml Log: Added missing [State: experimental] attribute AFAICS ps is not experimental: http://pecl.php.net/package/ps Friedhelm
Re: [PHP-DOC] MySQLi extension
Hi Philip, And, should we keep track (document) _when_ extensions became stable? Nice too have, but not really necessary, imho. Regards Friedhelm
[PHP-DOC] [Fwd: [DOC-WEB] 'make html' dumps output to console]
Hi, should appear on phpdoc. Friedhelm ---BeginMessage--- Hi, I've been making contributions to the PHP documentation for the IBM_DB2 functions and up until now I had no problems with the documentation tools, but when I tried to preview my changes by transforming to html this time typing 'make html' just dumps a whole bunch of output to the console really fast (I think it is text that would go in the html) and doesn't create any html files. I'm running Windows XP Pro SP2 and take the following steps: run cygwin checkout phpdoc prompt~ cd phpdoc prompt~ autoconf prompt~ ./configure prompt~ make test // This works fine prompt~ make test_xml // This works fine prompt~ make html // no errors, just dumbs to console and does nothing except removes html directory and copies in /html/figures folder and contents. To attempt to fix this I have reinstalled my PHP installation checked out peardoc and attempted 'make html' from there with the same result and make sure i checkout a completely fresh phpdoc and there's no change to this behaviour. If anybody knows of a way to fix this it would be greatly appeciated. Thanks, Owain Owain Jones [EMAIL PROTECTED] IBM DB2 Information Development IBM Toronto Lab Markham, ON (905)-413-2196 ---End Message---
Re: [PHP-DOC] MySQLi extension
Hi, Philip Olson wrote: - Original Message - This was already fixed in the English translation, so it's up to the Germans to catch up (-: On that note, Philip just said to me i wonder if we can create a way to store important items across translations, like for example, deprecated status (ex. mysqli from that thread) After a bit of brainstorming, we came up with the idea of creating extension-specific status entities that reference an extension's status, globally (because this sort of thing isn't translation specific). For example, we'd add new global entities: !ENTITY status.pecl.phar warn.experimental; !ENTITY status.ext.mysqli etc. (remember, warn.experimental; is translated) That way, this sort of thing would never happen (once the status.foo; entities make it into the various reference.xml files. bah.. the more the entities, the slower the build becomes. Hey, a computer is a tool to make things magically happen, even for translators ;-) I don't buy this argument without any rough figures. So, let's not interfere with translators work :P Nuno As Sean said: this sort of thing isn't translation specific. Sure it would add one new entity per extension (that would be used in each translation) so although this is a lot I don't feel the slower build time (wonder how much?) is reason enough to not do it. If we do this, the status of all extensions in every translation will be correct and doing this requires zero additional work for translators. Correctness counts more than build time no? Friedhelm
Re: [PHP-DOC] MySQLi extension
Sean Coates wrote: [...] That way, this sort of thing would never happen (once the status.foo; entities make it into the various reference.xml files. Thoughts? Big +1 Friedhelm
[PHP-DOC] #40088 [Opn-Bgs]: 'binary-safe' explanation needed in documentation
ID: 40088 Updated by: [EMAIL PROTECTED] Reported By: stepheneliotdewey at gmail dot com -Status: Open +Status: Bogus Bug Type: Documentation problem Operating System: irrelevant PHP Version: Irrelevant New Comment: Hi, the PHP-Manual is not the place to explain fundamental concepts. You can, for example, search the web to get the answer what binary-safe means. There is nothing php-specific about binary-safe. That said, don't expect the PHP-Manual to be the place to get explanations what common terms mean ;-) Friedhelm Previous Comments: [2007-01-10 13:08:56] stepheneliotdewey at gmail dot com Description: It would be good to include a description of what binary-safe means in PHP in the documentation along with some examples of differences between how functions would perform if they were and if they were not binary-safe. This would be helpful to users like myself who are not experienced with those concepts. -- Edit this bug report at http://bugs.php.net/?id=40088edit=1
[PHP-DOC] #36430 [Asn-Fbk]: Problem on Zend Overview
ID: 36430 Updated by: [EMAIL PROTECTED] Reported By: hugotacito at yahoo dot com dot br -Status: Assigned +Status: Feedback Bug Type:Documentation problem PHP Version: Irrelevant Assigned To: derick New Comment: http://www.php.net/manual/pt_BR/zend.overview.php shows the image. Previous Comments: [2006-03-07 01:31:58] [EMAIL PROTECTED] Derick, could you please copy or symlink the files there? They are in en/figures directory. [2006-02-17 18:10:26] hugotacito at yahoo dot com dot br Description: Theres a problem in the image of the manual in pt_BR... In the page http://www.php.net/manual/pt_BR/zend.overview.php the image of The internal structure of PHP doesn't appear, because the image could not be found... The image missing is http://br.php.net/manual/pt_BR/figures/Extending_Zend_1_PHPs_internal_structure.png -- Edit this bug report at http://bugs.php.net/?id=36430edit=1
Re: [PHP-DOC] Proposal to remove void from protos
Hi Jakub, Jakub Vrana wrote: Poll results: [...] Thank you for the opinions, I've added void to Pseudo-types. Thanks for adding ;-) Friedhelm
Re: [PHP-DOC] Proposal to remove void from protos
Dave Barr wrote: Jakub Vrana wrote: Hello! Would you agree with removal of the word void in methodsynpsis both from return type and parameters list? I propose to change the return type to null which it really is and remove it completely from parameters list as it is the way to declare that function doesn't accept any parameters in user-defined functions. New synopsis would be: null debug_print_backtrace() instead of: void debug_print_backtrace(void) Can't we add void to http://php.net/language.pseudo-types instead? +1 from me Friedhelm
Re: [PHP-DOC] Changing CVS acc. data
Lajos Cseppentõ wrote: Hello, How can I change my e-mail address and password of my CVS account? http://master.php.net/manage/users.php
Re: [PHP-DOC] cvs: phpdoc /en/install pecl.xml
Hi Pierre, Pierre-Alain Joye wrote: pajoye Thu Oct 19 21:09:02 2006 UTC Modified files: /phpdoc/en/install pecl.xml Log: - replace pear by pecl. pecl is the pecl.php.net installer (default channel of pecl is pecl.php.net not pear.php.net) And pecl is available as of PHP x.x.x? What should people use with versions = PHP x.x.x? Or is this an issue, which Version if PEAR is installed? Think, that should be in the docs. Friedhelm
Re: [PHP-DOC] cvs: phpdoc /en/install pecl.xml
Pierre wrote: [...] And pecl is available as of PHP x.x.x? What should people use with versions = PHP x.x.x? Or is this an issue, which Version if PEAR is installed? Think, that should be in the docs. PEAR 1.4.0 or earlier, available in all recent (and supported) PHP releases. The installation of the pecl command is done by the installer (gopear or with php releases). The question form my POV and maybe our users remain: Installed with php-release: pecl-command is available as of PHP x.x.x? in all recent (and supported) PHP releases is a vague term. There must be a PHP Version we can name, where pecl-command is installed first time, no? We should offer this piece of info to our readers :-) It has to be used to install pecl packages, not pear. Thanks, I know ;-) Friedhelm
Re: [PHP-DOC] cvs: phpdoc /en/install pecl.xml
Pierre wrote: Hello, On 10/21/06, Friedhelm Betz [EMAIL PROTECTED] wrote: Pierre wrote: [...] And pecl is available as of PHP x.x.x? What should people use with versions = PHP x.x.x? Or is this an issue, which Version if PEAR is installed? Think, that should be in the docs. PEAR 1.4.0 or earlier, available in all recent (and supported) PHP releases. The installation of the pecl command is done by the installer (gopear or with php releases). The question form my POV and maybe our users remain: Installed with php-release: pecl-command is available as of PHP x.x.x? in all recent (and supported) PHP releases is a vague term. There must be a PHP Version we can name, where pecl-command is installed first time, no? We should offer this piece of info to our readers :-) No idea, 5.1.0? Anyone? However, it is more important to introduce the notion of *installer* and package versions and not only php versions. I agree completly, that it is important to introduce the notion of *installer* version. But I didn't get the part about more important. More important than what? Don't get me wrong: but imagine someone is reading the docs, how to install a pecl-extension as outlined, fires up her terminal, types pecl install pecl-extension and pecl-command is not available? No hint in the docs, thats bad, whats going on ;-) Wchich steps should she take to get the required pecl-command or maybe she can still use pear install... ? Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/strings/functions str-repeat.xml
betzWed Oct 18 15:00:01 2006 UTC Modified files: /phpdoc/en/reference/strings/functions str-repeat.xml Log: fix 39186 http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/strings/functions/str-repeat.xml?r1=1.7r2=1.8diff_format=u Index: phpdoc/en/reference/strings/functions/str-repeat.xml diff -u phpdoc/en/reference/strings/functions/str-repeat.xml:1.7 phpdoc/en/reference/strings/functions/str-repeat.xml:1.8 --- phpdoc/en/reference/strings/functions/str-repeat.xml:1.7Tue Aug 17 21:44:35 2004 +++ phpdoc/en/reference/strings/functions/str-repeat.xmlWed Oct 18 15:00:01 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.7 $ -- +!-- $Revision: 1.8 $ -- !-- splitted from ./en/functions/strings.xml, last change in rev 1.2 -- refentry id=function.str-repeat refnamediv @@ -14,7 +14,7 @@ methodparamtypeint/typeparametermultiplier/parameter/methodparam /methodsynopsis para - Returns parameterinput_str/parameter repeated + Returns parameterinput/parameter repeated parametermultiplier/parameter times. parametermultiplier/parameter has to be greater than or equal to 0. If the parametermultiplier/parameter is set to 0, the function will
[PHP-DOC] #39186 [Opn-Csd]: Typo in str_repeat documentation: input_str
ID: 39186 Updated by: [EMAIL PROTECTED] Reported By: ca at lapage dot com -Status: Open +Status: Closed Bug Type:Documentation problem PHP Version: Irrelevant New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: [2006-10-18 13:45:10] ca at lapage dot com Description: 'input_str' should read 'input' on http://us3.php.net/manual/en/function.str-repeat.php -- Edit this bug report at http://bugs.php.net/?id=39186edit=1
Re: [PHP-DOC] Documenting coding standards
Hi, Philip Olson wrote: [...] We could link to PEAR. In the docs we use the PEAR coding standard for examples. We should not duplicate the infos from PEAR, imho. How about having the tutorial briefly talk about it (why it's good to do), and link to the PEAR coding standard. Fine with me. Talking about coding standards in general and *briefly*, linking to PEAR is fine with me ;-) And to go one step further: talking about documenting sourcecode and link to phpdocumentor? Seems a good idea to me ;-) Maybe in Hints and Tips ... Friedhelm
Re: [PHP-DOC] Documenting coding standards
Hi, Etienne Kneuss wrote: Hi, Currently, there is no official coding standards documented on php.net. Because of that, the coding standards of PEAR are often referenced in discussions. It may be useful to document some coding standards: indenting, whitespaces, directly on php.net, giving beginners rules/advices to code in a way that looks nice. [...] What do you think ? We could link to PEAR. In the docs we use the PEAR coding standard for examples. We should not duplicate the infos from PEAR, imho. Friedhelm
[PHP-DOC] #39031 [Opn-Ana]: call to undefined function in imageftbbox()
ID: 39031
Updated by: [EMAIL PROTECTED]
Reported By: vijijvs at yahoo dot co dot in
-Status: Open
+Status: Analyzed
Bug Type: Documentation problem
Operating System: Mandrake Linux
PHP Version: Irrelevant
New Comment:
imageftbbox, imagefttext requires freetype-support in gd.
your output from gd shows, that your gd is not compiled with
freetype-support.
Previous Comments:
[2006-10-05 04:31:52] vijijvs at yahoo dot co dot in
Following is the information got for gdinfo:
array(10) { [GD Version]= string(13) 2.0 or higher [FreeType
Support]= bool(false) [T1Lib Support]= bool(false) [GIF Read
Support]= bool(true) [GIF Create Support]= bool(true) [JPG
Support]= bool(true) [PNG Support]= bool(true) [WBMP
Support]= bool(true) [XBM Support]= bool(false) [JIS-mapped
Japanese Font Support]= bool(false) }
[2006-10-04 18:23:37] [EMAIL PROTECTED]
According to the source (gd.c):
ifdef ENABLE_GD_TTF
PHP_FE(imagettfbbox, arginfo_imagettfbbox)
PHP_FE(imagettftext, arginfo_imagettftext)
#if HAVE_LIBFREETYPE HAVE_GD_STRINGFTEX
PHP_FE(imageftbbox,
arginfo_imageftbbox)
PHP_FE(imagefttext,
arginfo_imagefttext)
#endif
#endif
Currently both imageftbbox() and imagefttext() have the undocumented
status so essentially this bug report asks them to be documented. There
are currently ~700* functions with the undocumented status but let's
leave this one open anyways...
* http://doc.php.net/php/undoc_functions.php
[2006-10-04 17:07:36] judas dot iscariote at gmail dot com
Your PHP is compiled against a GD version that doesn't support this.
what gdinfo says ?
?php
var_dump(gd_info());
?
[2006-10-04 06:52:03] vijijvs at yahoo dot co dot in
Description:
I get a fatal error:
Fatal error: Call to undefined function: imageftbbox()in php4.3.9 even
though other image functions are working.
Reproduce code:
---
$fontSize = 5;
$lineSpacing = 1;
list($llx, $lly, $lrx, $lry, $urx, $ury, $ulx, $uly) =
imageftbbox($fontSize, 0, $fontFileName, $text, array(linespacing =
$lineSpacing));
$textWidth = $lrx - $llx;
$textHeight = $lry - $ury;
$angle = 0;
Actual result:
--
Fatal error: Call to undefined function: imageftbbox()
--
Edit this bug report at http://bugs.php.net/?id=39031edit=1
[PHP-DOC] cvs: phpdoc /en/reference/image configure.xml
betzThu Oct 5 10:14:53 2006 UTC Modified files: /phpdoc/en/reference/image configure.xml Log: remove unrelated exif not for windows, clarify what T1 fonts are http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/image/configure.xml?r1=1.10r2=1.11diff_format=u Index: phpdoc/en/reference/image/configure.xml diff -u phpdoc/en/reference/image/configure.xml:1.10 phpdoc/en/reference/image/configure.xml:1.11 --- phpdoc/en/reference/image/configure.xml:1.10Tue Sep 14 09:26:27 2004 +++ phpdoc/en/reference/image/configure.xml Thu Oct 5 10:14:53 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.10 $ -- +!-- $Revision: 1.11 $ -- section id=image.installation reftitle.install; para @@ -17,12 +17,6 @@ removed in PHP 4.3.2. Also note that the preferred truecolor image functions, such as functionimagecreatetruecolor/function, require GD2. /para - note - para - To enable exif support in Windows, php_mbstring.dll must be loaded prior - to php_exif.dll in php.ini. - /para - /note para id=image.configure.php3 To disable GD support in emphasisPHP 3/emphasis add option role=configure--without-gd/option to your configure line. @@ -109,7 +103,7 @@ row entryliteralT1lib/literal/entry entry - To enable support for T1lib (Type 1 fonts) add + To enable support for T1lib (Postscript Type 1 fonts) add option role=configure--with-t1lib[=DIR]/option. /entry /row
[PHP-DOC] cvs: phpdoc /en/reference/image reference.xml
betzThu Oct 5 10:53:33 2006 UTC Modified files: /phpdoc/en/reference/image reference.xml Log: move exif info to intro, rewording http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/image/reference.xml?r1=1.27r2=1.28diff_format=u Index: phpdoc/en/reference/image/reference.xml diff -u phpdoc/en/reference/image/reference.xml:1.27 phpdoc/en/reference/image/reference.xml:1.28 --- phpdoc/en/reference/image/reference.xml:1.27Tue Jun 6 15:10:33 2006 +++ phpdoc/en/reference/image/reference.xml Thu Oct 5 10:53:33 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.27 $ -- +!-- $Revision: 1.28 $ -- !-- Purpose: utilspec.image -- !-- Membership: bundled -- @@ -26,11 +26,20 @@ acronymTIFF/acronym and acronymJPEG2000/acronym images. /para para + With the link linkend=ref.exifexif extension/link, you are able + to work with information stored in headers of + acronymJPEG/acronym and acronymTIFF/acronym images. This way you can + read meta data generated by digital cameras. The exif + functions do not require the acronymGD/acronym library. +/para + +para note simpara - Read requirements section about how to expand image capabilities - to read, write and modify images and to read meta data of pictures - taken by digital cameras. + Read the requirements section about how to expand image capabilities + to read, write and modify images. To read meta data of pictures + taken by digital cameras you need the above mentioned + link linkend=ref.exifexif extension/link. /simpara /note /para @@ -143,21 +152,13 @@ entryliteralT1lib/literal/entry entryulink url=url.t1lib;url.t1lib;/ulink)/entry entry - Support for Type 1 fonts. + Support for Postscript Type 1 fonts. /entry /row /tbody /tgroup /table /para - -para - If you have PHP compiled with option role=configure--enable-exif/option - you are able to work with information stored in headers of - acronymJPEG/acronym and acronymTIFF/acronym images. This way you can - read meta data generated by digital cameras as mentioned above. These - functions do not require the acronymGD/acronym library. -/para /section reference.image.configure;
[PHP-DOC] cvs: phpdoc /en language-snippets.ent
betzThu Oct 5 16:16:16 2006 UTC Modified files: /phpdoc/en language-snippets.ent Log: note about freetype requirement http://cvs.php.net/viewvc.cgi/phpdoc/en/language-snippets.ent?r1=1.173r2=1.174diff_format=u Index: phpdoc/en/language-snippets.ent diff -u phpdoc/en/language-snippets.ent:1.173 phpdoc/en/language-snippets.ent:1.174 --- phpdoc/en/language-snippets.ent:1.173 Fri Sep 8 08:56:01 2006 +++ phpdoc/en/language-snippets.ent Thu Oct 5 16:16:16 2006 @@ -1,4 +1,4 @@ -!-- $Revision: 1.173 $ -- +!-- $Revision: 1.174 $ -- !-- Keep 'em sorted -- @@ -225,6 +225,10 @@ !ENTITY note.gd.2 'notesimparaThis function requires GD 2.0.1 or later (2.0.28 or later is recommended)./simpara/note' +!ENTITY note.freetype 'notesimparaThis function is only available if +PHP is compiled with freetype support (option role=configure--with-freetype-dir=DIR/option) +/simpara/note' + !-- Date and time entities -- !ENTITY date.timezone.errors.description 'para Every call to a date/time function will generate a constantE_NOTICE/constant
[PHP-DOC] cvs: phpdoc /en/reference/image/functions imageftbbox.xml imagefttext.xml
betzThu Oct 5 16:18:12 2006 UTC Modified files: /phpdoc/en/reference/image/functionsimageftbbox.xml imagefttext.xml Log: fix #39031, funcs require freetype support http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/image/functions/imageftbbox.xml?r1=1.5r2=1.6diff_format=u Index: phpdoc/en/reference/image/functions/imageftbbox.xml diff -u phpdoc/en/reference/image/functions/imageftbbox.xml:1.5 phpdoc/en/reference/image/functions/imageftbbox.xml:1.6 --- phpdoc/en/reference/image/functions/imageftbbox.xml:1.5 Thu Sep 16 15:02:51 2004 +++ phpdoc/en/reference/image/functions/imageftbbox.xml Thu Oct 5 16:18:12 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.5 $ -- +!-- $Revision: 1.6 $ -- !-- splitted from ./en/functions/image.xml, last change in rev 1.67 -- refentry id='function.imageftbbox' refnamediv @@ -19,6 +19,7 @@ para warn.undocumented.func; note.gd.2; + note.freetype; /para note para http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/image/functions/imagefttext.xml?r1=1.6r2=1.7diff_format=u Index: phpdoc/en/reference/image/functions/imagefttext.xml diff -u phpdoc/en/reference/image/functions/imagefttext.xml:1.6 phpdoc/en/reference/image/functions/imagefttext.xml:1.7 --- phpdoc/en/reference/image/functions/imagefttext.xml:1.6 Thu Sep 16 15:02:51 2004 +++ phpdoc/en/reference/image/functions/imagefttext.xml Thu Oct 5 16:18:12 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- splitted from ./en/functions/image.xml, last change in rev 1.67 -- refentry id='function.imagefttext' refnamediv @@ -23,6 +23,7 @@ para warn.undocumented.func; note.gd.2; + note.freetype; /para note para
[PHP-DOC] #39031 [Ana-Csd]: call to undefined function in imageftbbox()
ID: 39031
Updated by: [EMAIL PROTECTED]
Reported By: vijijvs at yahoo dot co dot in
-Status: Analyzed
+Status: Closed
Bug Type: Documentation problem
Operating System: Mandrake Linux
PHP Version: Irrelevant
New Comment:
Still undocumented, but freetype requirement mentioned.
Previous Comments:
[2006-10-05 08:54:34] [EMAIL PROTECTED]
imageftbbox, imagefttext requires freetype-support in gd.
your output from gd shows, that your gd is not compiled with
freetype-support.
[2006-10-05 04:31:52] vijijvs at yahoo dot co dot in
Following is the information got for gdinfo:
array(10) { [GD Version]= string(13) 2.0 or higher [FreeType
Support]= bool(false) [T1Lib Support]= bool(false) [GIF Read
Support]= bool(true) [GIF Create Support]= bool(true) [JPG
Support]= bool(true) [PNG Support]= bool(true) [WBMP
Support]= bool(true) [XBM Support]= bool(false) [JIS-mapped
Japanese Font Support]= bool(false) }
[2006-10-04 18:23:37] [EMAIL PROTECTED]
According to the source (gd.c):
ifdef ENABLE_GD_TTF
PHP_FE(imagettfbbox, arginfo_imagettfbbox)
PHP_FE(imagettftext, arginfo_imagettftext)
#if HAVE_LIBFREETYPE HAVE_GD_STRINGFTEX
PHP_FE(imageftbbox,
arginfo_imageftbbox)
PHP_FE(imagefttext,
arginfo_imagefttext)
#endif
#endif
Currently both imageftbbox() and imagefttext() have the undocumented
status so essentially this bug report asks them to be documented. There
are currently ~700* functions with the undocumented status but let's
leave this one open anyways...
* http://doc.php.net/php/undoc_functions.php
[2006-10-04 17:07:36] judas dot iscariote at gmail dot com
Your PHP is compiled against a GD version that doesn't support this.
what gdinfo says ?
?php
var_dump(gd_info());
?
[2006-10-04 06:52:03] vijijvs at yahoo dot co dot in
Description:
I get a fatal error:
Fatal error: Call to undefined function: imageftbbox()in php4.3.9 even
though other image functions are working.
Reproduce code:
---
$fontSize = 5;
$lineSpacing = 1;
list($llx, $lly, $lrx, $lry, $urx, $ury, $ulx, $uly) =
imageftbbox($fontSize, 0, $fontFileName, $text, array(linespacing =
$lineSpacing));
$textWidth = $lrx - $llx;
$textHeight = $lry - $ury;
$angle = 0;
Actual result:
--
Fatal error: Call to undefined function: imageftbbox()
--
Edit this bug report at http://bugs.php.net/?id=39031edit=1
[PHP-DOC] cvs: phpdoc /en/reference/icap reference.xml
betzThu Oct 5 16:32:29 2006 UTC Modified files: /phpdoc/en/reference/icap reference.xml Log: icap _is_ removed http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/icap/reference.xml?r1=1.5r2=1.6diff_format=u Index: phpdoc/en/reference/icap/reference.xml diff -u phpdoc/en/reference/icap/reference.xml:1.5 phpdoc/en/reference/icap/reference.xml:1.6 --- phpdoc/en/reference/icap/reference.xml:1.5 Sun Sep 4 19:39:15 2005 +++ phpdoc/en/reference/icap/reference.xml Thu Oct 5 16:32:29 2006 @@ -1,9 +1,9 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.5 $ -- +!-- $Revision: 1.6 $ -- !-- State: deprecated -- reference id=ref.icap - titleICAP Functions [deprecated]/title + titleICAP Functions [removed]/title titleabbrevICAP/titleabbrev partintro @@ -11,7 +11,7 @@ reftitle.intro; note simpara - Icap will be removed in near future. Neither this module, nor + Icap was removed from PHP. Neither this module, nor those versions of icap library are supported any longer. If you want to use calendar capabilities in PHP, use link linkend=ref.mcalmcal/link instead.
Re: [PHP-DOC] user notes and spam
Nuno Lopes wrote: sure, I'll remove it. Nuno Thx ;-) Friedhelm
[PHP-DOC] #38443 [Fbk]: missing how to REALLY install win, apache2.2.3
ID: 38443 Updated by: [EMAIL PROTECTED] Reported By: indexsuxx at freemail dot hu Status: Feedback Bug Type: Documentation problem Operating System: XP PHP Version: Irrelevant New Comment: he is talking about apache 2.2.x ;-) not 2.0 Previous Comments: [2006-08-13 14:20:30] [EMAIL PROTECTED] what part doesn't work? I've windows xp+apache 2.0+php 5 working and I've installed PHP using the installation guide we provide. [2006-08-13 13:54:02] indexsuxx at freemail dot hu Description: The given installation giude simply does not work on win xp, apache 2.2.3 (and I think nowhere else). Just try google on/Apache2.2/conf/httpd.conf: Cannot load C:/php/php5apache2.dll into server: The specified module could not be found to see how many people get this problem. Yeah, I know run apache on a real OS and not on XP but if it is allowed then it should be writen in a usable way. I suggest it for consideration. -- Edit this bug report at http://bugs.php.net/?id=38443edit=1
Re: [PHP-DOC] ca3.php.net with print function
Jean-Sébastien Goupil wrote: Yo When searching for print function on ca3.php.net, it returns CSS... http://ca3.php.net/print returns : http://ca3.php.net/print.css other servers return the print function... What's wrong ? Miror specific problem? Maybe you should write to [EMAIL PROTECTED] Friedhelm
Re: [PHP-DOC] Re: [PHP-NOTES] Note spam
Sean Coates wrote: [resend: not sure why this didn't make it through, yesterday; re-sending; sorry if it's a dupe -S] Nuno Lopes wrote: Well we have already tried a couple of methods but none of them worked so far, including DNS blacklists, spamassassin and a simple words blacklisting. I've run out of ideas. Training spamassassin would probably work, but I'm not sure if it wouldn't cause disturbs in the mail server. Did we drop the double opt-in idea? - User submits a note (with valid email address) - We send mail with a token URL - User clicks URL - Note is approved and posted Do we need to approve? I guess we have not enough man-power for that. Simply post the note after we receive the token. Max 5 notes per address per day. Or x notes per domain/IP per day.. x notes per domain/IP per day will for sure not work. Think of people behind proxies We should not limit the notes per day. To much to track, imho, no? Yes, the evil side COULD be automated, but it's a lot more difficult than a simple post. I like this proposal, but Nuno's point stands: who's gonna implement that? Friedhelm
Re: [PHP-DOC] Re: [PHP-NOTES] Note spam
Sean Coates wrote: Do we need to approve? I guess we have not enough man-power for that. Simply post the note after we receive the token. That's what I meant. Note is approved when the token URL is clicked. Ah, sorry, my misunderestimating or something this way ;-) Max 5 notes per address per day. Or x notes per domain/IP per day.. x notes per domain/IP per day will for sure not work. Think of people behind proxies We should not limit the notes per day. To much to track, imho, no? I suspect that these spammers would just register example.com and create [EMAIL PROTECTED] [EMAIL PROTECTED] etc. Yes, possible, but we can see and implement upperbound limit later ;-) Yes, the evil side COULD be automated, but it's a lot more difficult than a simple post. I like this proposal, but Nuno's point stands: who's gonna implement that? Not sure. (-: I'd love to find time to do it, but I don't have it right now. Either way, notes are a mess. Yes. Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/ssh2/functions ssh2-sftp-mkdir.xml ssh2-sftp-rmdir.xml
betzThu Mar 16 11:10:22 2006 UTC
Modified files:
/phpdoc/en/reference/ssh2/functions ssh2-sftp-mkdir.xml
ssh2-sftp-rmdir.xml
Log:
typo in examples, spotted byuser notes
http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/ssh2/functions/ssh2-sftp-mkdir.xml?r1=1.4r2=1.5diff_format=u
Index: phpdoc/en/reference/ssh2/functions/ssh2-sftp-mkdir.xml
diff -u phpdoc/en/reference/ssh2/functions/ssh2-sftp-mkdir.xml:1.4
phpdoc/en/reference/ssh2/functions/ssh2-sftp-mkdir.xml:1.5
--- phpdoc/en/reference/ssh2/functions/ssh2-sftp-mkdir.xml:1.4 Thu Dec 30
19:27:07 2004
+++ phpdoc/en/reference/ssh2/functions/ssh2-sftp-mkdir.xml Thu Mar 16
11:10:22 2006
@@ -1,5 +1,5 @@
?xml version='1.0' encoding='iso-8859-1'?
-!-- $Revision: 1.4 $ --
+!-- $Revision: 1.5 $ --
!-- Generated by xml_proto.php v2.1. Found in /scripts directory of phpdoc.
--
refentry id=function.ssh2-sftp-mkdir
refnamediv
@@ -32,7 +32,7 @@
programlisting role=php
![CDATA[
?php
-$connection = ssh2_connet('shell.example.com', 22);
+$connection = ssh2_connect('shell.example.com', 22);
ssh2_auth_password($connection, 'username', 'password');
$sftp = ssh2_sftp($connection);
http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/ssh2/functions/ssh2-sftp-rmdir.xml?r1=1.3r2=1.4diff_format=u
Index: phpdoc/en/reference/ssh2/functions/ssh2-sftp-rmdir.xml
diff -u phpdoc/en/reference/ssh2/functions/ssh2-sftp-rmdir.xml:1.3
phpdoc/en/reference/ssh2/functions/ssh2-sftp-rmdir.xml:1.4
--- phpdoc/en/reference/ssh2/functions/ssh2-sftp-rmdir.xml:1.3 Tue Jan 4
10:36:43 2005
+++ phpdoc/en/reference/ssh2/functions/ssh2-sftp-rmdir.xml Thu Mar 16
11:10:22 2006
@@ -1,5 +1,5 @@
?xml version='1.0' encoding='iso-8859-1'?
-!-- $Revision: 1.3 $ --
+!-- $Revision: 1.4 $ --
!-- Generated by xml_proto.php v2.1. Found in /scripts directory of phpdoc.
--
refentry id=function.ssh2-sftp-rmdir
refnamediv
@@ -27,7 +27,7 @@
programlisting role=php
![CDATA[
?php
-$connection = ssh2_connet('shell.example.com', 22);
+$connection = ssh2_connect('shell.example.com', 22);
ssh2_auth_password($connection, 'username', 'password');
$sftp = ssh2_sftp($connection);
[PHP-DOC] #36740 [Opn-Bgs]: Function ob-start: Wrong param count
ID: 36740 Updated by: [EMAIL PROTECTED] Reported By: php at cconstruct dot de -Status: Open +Status: Bogus Bug Type: Documentation problem Operating System: Gentoo Linux/AMD64 PHP Version: Irrelevant New Comment: The german manual is outdated. If you want to help translating the manual to german, please contact [EMAIL PROTECTED] Friedhelm Previous Comments: [2006-03-15 03:55:37] php at cconstruct dot de Description: The german manual on the function ob-start, residing at http://de.php.net/manual/de/function.ob-start.php, is mistaken in the parameter count of the function ob-start. Reproduce code: --- Visit http://de.php.net/manual/de/function.ob-start.php and compare to e.g. http://de.php.net/manual/en/function.ob-start.php Expected result: Two times the same parameter count: bool ob_start ( [callback output_callback [, int chunk_size [, bool erase]]] ) Actual result: -- In the german version it says: void ob_start ( void ) -- Edit this bug report at http://bugs.php.net/?id=36740edit=1
Re: [PHP-DOC] cvs: phpdoc /en/reference/fileinfo reference.xml
Jakub Vrana wrote: vrana Thu Mar 9 14:19:20 2006 UTC Modified files: /phpdoc/en/reference/fileinfo reference.xml Log: Experimental http://pecl.php.net/package/Fileinfo Latest Release is stable. Friedhelm
Re: [PHP-DOC] cvs: phpdoc /en/reference/fileinfo reference.xml
Jakub Vrana wrote: Friedhelm Betz wrote: Latest Release is stable. In CVS, there is still EXPERIMENTAL file. Should this file be deleted? Ask the maintainer, Ilia;-) IMHO yes Friedhelm
Re: [PHP-DOC] cvs: phpdoc /en/appendices ini.xml
Gavin Foster wrote: Hi, I expected the below modification to add a description to this section of the online manual: http://www.php.net/manual/en/ini.core.php#ini.sql.safe-mode Can someone confirm that I've added the description to the correct file. Yes. My understanding was that the online manual is re-generated on a daily basis (assuming it is updated ever day), but it hasn't changed. No, it is not generated on a daily basis, only from time to time. Friedhelm
[PHP-DOC] #36619 [Opn]: broken hyperlink
ID: 36619 Updated by: [EMAIL PROTECTED] Reported By: ming dot khor at gmail dot com Status: Open -Bug Type: Website problem +Bug Type: Documentation problem Operating System: Irrelevant PHP Version: Irrelevant New Comment: changed category Friedhelm Previous Comments: [2006-03-05 15:02:08] ming dot khor at gmail dot com Description: It seems that following hyperlink located at this webpage (http://us2.php.net/manual/en/faq.general.php) is broken: Free On-Line Dictionary of Computing. The URL seems to be invalid? -- Edit this bug report at http://bugs.php.net/?id=36619edit=1
Re: [PHP-DOC] php.net search data aggregation
Rasmus Lerdorf wrote: Not sure if we can gleam enough out of this to try to adapt the documentation or the web site redirection keywords, but it might be worth a try. See: http://www.php.net/~rasmus/sum.php We should give a try. php.net/changelog - php.net/ChangeLog-5.php, on that page link to ChangeLog-4.php Make ini-settings shortcuts and/or new search category ini-settings. Along with the note statistics and maybe Manual pages most active top 20 from http://doc.php.net/php/notes_stats.php we can identify the parts of the manual to be improved. Regards Friedhelm
Re: [PHP-DOC] php.net search data aggregation
Hi Sean, Sean Coates wrote: PHP 5 uptake is also speeding up and there are a couple of areas of the manual that are confusing. A search for xml or going to php.net/xml lands you on php.net/manual/en/ref.xml.php which has no mention of the different xml implementations available. The best way to handle this, probably, is to add a very high level XML Processing in PHP appendix and link xml there. The appendix could then link the the various sections: DOM, libxml, SimpleXML, ref.xml, etc. Alternative: Let the search handle this ambiguous terms and nuke this kinds of shortcuts? php.net/xml would give you a page with results relevant to xml, of course extension/implementation wise. The point Rasmus made boils probably down to categorized manual http://cvs.php.net/viewcvs.cgi/phpdoc/RFC/manual.xml.in?view=markuprev=1.19 This approach would it make dead simple, php.net/xml points to refgroup id=refs.xml This said, I don't know the status of livedocs and in which way livedocs supersedes the categorized manual approach. Friedhelm
[PHP-DOC] #36603 [Opn-Bgs]: Documentation references to PHP6
ID: 36603 Updated by: [EMAIL PROTECTED] Reported By: kills at online dot de -Status: Open +Status: Bogus Bug Type:Documentation problem PHP Version: Irrelevant New Comment: Yes, we are documenting PHP 6 too, although it is not released yet. You can find documentation for PHP 6 in various other places in the manual. Thanks Friedhelm Previous Comments: [2006-03-03 11:38:17] kills at online dot de Description: Hi, in the documentation there is something written about PHP6: http://www.php.net/manual/en/function.sort.php [quote] SORT_LOCALE_STRING - compare items as strings, based on the current locale. Added in PHP 4.4.0 and 5.0.2. Before PHP 6, it uses the system locale, which can be changed using setlocale(). Since PHP 6, you must use the i18n_loc_set_default() function. [/quote] Bye, Markus -- Edit this bug report at http://bugs.php.net/?id=36603edit=1
Re: [PHP-DOC] Gabor resigns from the editor post
Gabor Hojtsy wrote: Friedhelm Betz wrote: Gabor Hojtsy wrote: Gabor Hojtsy wrote: To be constructive, I propose Nuno for a new editor (if he agrees). He has good overview necessary for this position and more than enough skills. I think he has respect from most docteam members. Good candidate. He has a good view on phpdoc, phpweb, user notes, livedocs, etc. Let's gather candidates and/or vote on the already proposed ones. Other votes or candidates? Vrana, Sean. We can have more than one person as Editor, no? Yes, you can. Depends on the team choice, if you would like to have :) there used to be multiple editors. I prefer more than one person;-) Friedhelm
Re: [PHP-DOC] Gabor resigns from the editor post
Hi Goba, Gabor Hojtsy wrote: Hi, I have been pondering through this writeup in the last couple of weeks, and the recent OSCOM events [1] prompted me to be straight and honest, and step back from the leadership of the PHP Documentation and from the list on the documentation frontpage consequently. That is bad news for the doc-team, because I always appreciated your clear, unagitated, constructive, well thought and friendly manner to contribute to the documentation. Yeah, let me say: your contribution was always very welcome and much valuable. Remembering back the days I joined phpdoc, you have been always around, answering questions for newbies like I was, improving, discussing, heck: you have been nearly everywhere. [...] I hope that my reasons are understandable, and I am certain that we will be able to manage to execute some smooth process of handing the reposibilities and the credits over. It was a great pleasure to work with you, and shape the PHP Documentation into what it is today. Your reasons are very understandable! Once I had the pleasure to meet you in real life (docmeeting linuxtag) and I can certainly say: it was always a great pleasure to work with you! So;), I wish you all the best for your past-phpdoc-life, thanks for your valuable time you spent for this project in the recent years. And maybe once you will be a famous hungarian actor;-? So, thanks again, best wishes, good by Friedhelm
Re: [PHP-DOC] Gabor resigns from the editor post
Hi Goba, Gabor Hojtsy wrote: I hope that my reasons are understandable, and I am certain that we will be able to manage to execute some smooth process of handing the reposibilities and the credits over. It was a great pleasure to work with you, and shape the PHP Documentation into what it is today. Your reasons are very understandable! Once I had the pleasure to meet you in real life (docmeeting linuxtag) and I can certainly say: it was always a great pleasure to work with you! So;), I wish you all the best for your past-phpdoc-life, thanks for your valuable time you spent for this project in the recent years. And maybe once you will be a famous hungarian actor;-? I would hand out invites four our May premier nights, but the play is in Hungarian, and I am afraid, not many of you would understand a word of it, even if you would be able to make it :) Hungarian? Huh ;-) Before I try to learn Hungarian I should improve my English;-) Anyhow it may be fun? But Hungary is a bit far;-) If you play in Germany on your world tour, i will come, for sure;-) All jokes aside: good luck for your premier nights! By the way, I am around at phpweb, and took par in the introduction of the Yahoo Search API based website search deployed today. Give it a try, give suggestions at the webmaster address! I will try it out, later... Friedhelm
Re: [PHP-DOC] spam protection for user notes
Hi Sean, Sean Coates wrote: [...] I'd prefer the dual-opt-in-like behaviour where the user is mailed and asked to confirm that he/she submitted the note. After say 10 unconfirmed mails by a particular address, they could get blacklisted. +1 for this solution, if spamassasin does not work. BTW, I just made some changes to the notes scripts to use new, shorter URLs. Thanks, much better! Friedhelm
Re: [PHP-DOC] #36535 [NEW]: Error in mysql_errno documentation (Polish version)
pkoszulinski at gmail dot com wrote: From: pkoszulinski at gmail dot com Operating system: PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: Error in mysql_errno documentation (Polish version) Description: On http://www.php.net/manual/pl/function.mysql-errno.php there is: Zwraca numer b#322;#281;du ostatniej operacji MySQL lub 0 (zero) je#347;li wyst#261;pi b#322;#261;d. but there should be: Zwraca numer b#322;#281;du ostatniej operacji MySQL lub 0 (zero) je#347;li NIE wyst#261;pi b#322;#261;d. Are their serious problems on the server-site or the client-site? Also this crappy encodings can be seen recently on php-notes. Thanks Friedhelm
Re: [PHP-DOC] #36535 [NEW]: Error in mysql_errno documentation (Polishversion)
Nuno Lopes wrote: pkoszulinski at gmail dot com wrote: From: pkoszulinski at gmail dot com Operating system: PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: Error in mysql_errno documentation (Polish version) Description: On http://www.php.net/manual/pl/function.mysql-errno.php there is: Zwraca numer b#322;#281;du ostatniej operacji MySQL lub 0 (zero) je#347;li wyst#261;pi b#322;#261;d. but there should be: Zwraca numer b#322;#281;du ostatniej operacji MySQL lub 0 (zero) je#347;li NIE wyst#261;pi b#322;#261;d. Are their serious problems on the server-site or the client-site? Also this crappy encodings can be seen recently on php-notes. Yep, I think this happened when the main site was moved to the new Yahoo server. Maybe it has some mbstring/filter/.. option that is passing the data through htmlentities() or similar. Should I file a bug-report or is it better to bug system@, group@, aeh, which one? Friedhelm
[PHP-DOC] #23714 [Opn]: Unix/HP-UX install documentation is outdated
ID: 23714 Updated by: [EMAIL PROTECTED] Reported By: ch at bumerang dot ro Status: Open Bug Type: Documentation problem Operating System: HPUX PHP Version: Irrelevant New Comment: Patch, diffed against the current xml-file are very welcome. Generic, uptodate, install instructions for HP UX is valuable for the manual. Thanks Friedhelm Previous Comments: [2006-02-22 23:02:43] flconseil at yahoo dot fr Yes, The HPWS package from HP is a solution, but I wanted to compile the package by myself because I have several Unix flavors to manage and I want them to have the same software versions, and to be able to regenerate it when I want, instead of waiting for HP. Another reason is that I have tried to get some help from HP, in order to know how they compile their package, and it has proved to be absolutely impossible to get any information. I don't like this kind of behavior. As I discovered later when doing it by myself, because of problems related to the HP-UX OS itself, they practically force most users to depend on their package. It is not my view of Open SOurce philosophy. As most of these big companies, they like to take, but not to give... So, I sent several days compiling a full Apache 2.0 + PHP 5.1.2 package, including every libraries they depend on. This package also includes most Apache modules and PHP extensions (zlib, SSL, LDAP, iconv, expat, xml, xslt, gd, png, Xpm, jpeg, freetype, bzip2, curl, MySQL, PostgreSQL, Oracle, AdoDB). I have also written a complete howto document, describing how to build everything from scratch, from the place to get the source packages, to the way to check that everything works OK. This document is available at : http://flaupretre.free.fr/redir.php?key=build_apa_hpux I am ready to write a 1 or 2 page resume of the document for the PHP documentation page (the full document is about 13 page long), with a link to the full document, for instance. Tell me what you think about it. [2005-05-07 05:00:02] [EMAIL PROTECTED] I believe the best method for installing PHP (and Apache) is to go here: http://www.software.hp.com/ And install one of the found packages. Searching for PHP yields several packages, for example: HP-UX Apache-based Web Server v.2.11 powered by Apache, Tomcat, Webmin We should most likely remove all current documentation and simply mention how to install one of these packages. Well, at least until someone who knows HP-UX can add additional information. [2005-04-26 17:41:22] [EMAIL PROTECTED] wk at mailstation dot de, can you please write some notes for current version or at least point us to sources you used? Everlasting honor will be yours :-). [2004-10-20 13:39:06] wk at mailstation dot de I have installed PHP 4.x and 5.x on HP-UX 10.xx and 11.xx. a) The documentation *is* outdated and even wrong (e. g., you *can* build PHP as a shared module on HP-UX). The reference to an unspecified Apache page is misleading even. b) No, take it out completely. Having nothing about HP-UX is better than that stuff. c) is therefor irrelevant. [2003-05-20 14:15:52] [EMAIL PROTECTED] The documentation itself needs an update, the file in question: phpdoc/en/chapters/install.hpux.xml A few points: a) The documentation was written for PHP 4.0.4 so maybe it's outdated? It at least looks outdated. b) It's time we move it from email format to doc format c) The links themselves are dead and should be presented in a more flexible way. Instead of linking to specific versions, how about refer to the needed libraries plus a generic link, such as: http://hpux.connect.org.uk/ftp/hpux/Gnu/ So until someone knows (not guesses) the answer to (a), implements (b), and (c), this report should remain open. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/23714 -- Edit this bug report at http://bugs.php.net/?id=23714edit=1
[PHP-DOC] spam protection for user notes
Hi all, user notes are spammed in recent days/weeks. Should we protect the submission form in some sane way (CAPTCHA)? Friedhelm
Re: [PHP-DOC] spam protection for user notes
Derick Rethans wrote: On Tue, 21 Feb 2006, Dan Scott wrote: Spammers suck. I would be in favour of implementing a basic mathematical skill-testing question a la Lukas Smith's blog at http://pooteeweet.org -- it is a protection method that is still accessible to the visually impaired, unlike classic CAPTCHA. Agreed, spammers suck, but CAPTCHAs too. Yeah, I don't like CAPTCHAs either. Mainly for the reason Dan outlined. Don't let the spammers win! :) Not at all ;-) What about: basic mathematical skill-testing question ? Friedhelm
Re: [PHP-DOC] cvs: phpdoc /en/reference/strings/functions stripos.xml strpos.xml strrpos.xml
Nuno Lopes wrote: vrana Fri Feb 17 12:33:11 2006 UTC Modified files: /phpdoc/en/reference/strings/functions stripos.xml strpos.xml strrpos.xml Log: False doesn't cause mixed (howto/working) Yeah I know! I've already read/change it several times. Quoting howto: Do not use mixed, if the return value is of a certain (not boolean) type, and FALSE only on error. Provide the primary return type as the return type of the function, and write down in the explanation, that it returns FALSE on error. Use return.success; if the function returns TRUE on success, and FALSE on failure. These functions return FALSE on normal operation, not on error. mysql_connect() for example returns a resource on success or false on failure. there you shoudn't use mixed. In this case, the return of false means not found, not a error, ence the use of mixed. (those pages even have the entity to explain how to use the === operator..) Hm, that's arguable. I might argue, that the main purpose is to find the position in a given string: normal operation. If not found, this might be an error or failure. Friedhelm
Re: [PHP-DOC] cvs: phpdoc /en/reference/strings/functions stripos.xml strpos.xml strripos.xml strrpos.xml
Nuno Lopes wrote: nlopess Fri Feb 17 12:17:20 2006 UTC Modified files: /phpdoc/en/reference/strings/functions stripos.xml strpos.xml strripos.xml strrpos.xml Log: fix return type, per user note I am certain, we decided to document as return type the main type of the returned value. There are many other funcs returning boolean false in case of failure. I think, mixed is not the propper return type in this case. Ah, Jakub was as always very fast;-) Friedhelm
[PHP-DOC] #36406 [Opn-Bgs]: different documentation of exit()+ die()
ID: 36406 Updated by: [EMAIL PROTECTED] Reported By: p dot bodnar at centrum dot cz -Status: Open +Status: Bogus Bug Type:Documentation problem PHP Version: Irrelevant New Comment: Other languages might catch up translation, when their volunteers find some spare time. Previous Comments: [2006-02-16 01:08:57] p dot bodnar at centrum dot cz Description: Functions exit() and die() are documented differently - with a different meaning - in English VS in other languages (found f.e. for Czech and German). [2006-02-16 01:05:35] p dot bodnar at centrum dot cz Description: Functions exit() and die() are documented differently - with a different meaning - in english VS in other languages (for cs and de, maybe other languages as well). -- Edit this bug report at http://bugs.php.net/?id=36406edit=1
[PHP-DOC] cvs: phpdoc /en/reference/imap/functions imap-alerts.xml imap-errors.xml imap-last-error.xml
betzSun Feb 12 18:57:46 2006 UTC Modified files: /phpdoc/en/reference/imap/functions imap-alerts.xml imap-errors.xml imap-last-error.xml Log: return values clarified, integrated user notes http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/imap/functions/imap-alerts.xml?r1=1.2r2=1.3diff_format=u Index: phpdoc/en/reference/imap/functions/imap-alerts.xml diff -u phpdoc/en/reference/imap/functions/imap-alerts.xml:1.2 phpdoc/en/reference/imap/functions/imap-alerts.xml:1.3 --- phpdoc/en/reference/imap/functions/imap-alerts.xml:1.2 Wed Apr 17 06:39:15 2002 +++ phpdoc/en/reference/imap/functions/imap-alerts.xml Sun Feb 12 18:57:46 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- !-- splitted from ./en/functions/imap.xml, last change in rev 1.33 -- refentry id=function.imap-alerts refnamediv @@ -19,9 +19,9 @@ para This function returns an array of all of the IMAP alert messages generated since the last functionimap_alerts/function call, - or the beginning of the page. When - functionimap_alerts/function is called, the alert stack is - subsequently cleared. The IMAP specification requires that these + or the beginning of the page. Returns false; if no alert messages are + available.When functionimap_alerts/function is called, the alert + stack is subsequently cleared. The IMAP specification requires that these messages be passed to the user. /para /refsect1 http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/imap/functions/imap-errors.xml?r1=1.4r2=1.5diff_format=u Index: phpdoc/en/reference/imap/functions/imap-errors.xml diff -u phpdoc/en/reference/imap/functions/imap-errors.xml:1.4 phpdoc/en/reference/imap/functions/imap-errors.xml:1.5 --- phpdoc/en/reference/imap/functions/imap-errors.xml:1.4 Fri Aug 20 09:36:58 2004 +++ phpdoc/en/reference/imap/functions/imap-errors.xml Sun Feb 12 18:57:46 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.4 $ -- +!-- $Revision: 1.5 $ -- !-- splitted from ./en/functions/imap.xml, last change in rev 1.33 -- refentry id=function.imap-errors refnamediv @@ -19,9 +19,9 @@ para This function returns an array of all of the IMAP error messages generated since the last functionimap_errors/function call, - or the beginning of the page. When - functionimap_errors/function is called, the error stack is - subsequently cleared. + or the beginning of the page. Returns false; if no error messages are + available. When functionimap_errors/function is called, the error + stack is subsequently cleared. /para para See also: functionimap_last_error/function. http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/imap/functions/imap-last-error.xml?r1=1.3r2=1.4diff_format=u Index: phpdoc/en/reference/imap/functions/imap-last-error.xml diff -u phpdoc/en/reference/imap/functions/imap-last-error.xml:1.3 phpdoc/en/reference/imap/functions/imap-last-error.xml:1.4 --- phpdoc/en/reference/imap/functions/imap-last-error.xml:1.3 Mon Mar 8 09:18:41 2004 +++ phpdoc/en/reference/imap/functions/imap-last-error.xml Sun Feb 12 18:57:46 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.3 $ -- +!-- $Revision: 1.4 $ -- !-- splitted from ./en/functions/imap.xml, last change in rev 1.33 -- refentry id=function.imap-last-error refnamediv @@ -20,7 +20,7 @@ message that occurred on the current page. The error stack is untouched; calling functionimap_last_error/function subsequently, with no intervening errors, will return the same - error. + error. Returns false; if no error messages are available. /para para See also: functionimap_errors/function.
[PHP-DOC] cvs: phpdoc /en/language control-structures.xml
betzSun Feb 12 19:52:23 2006 UTC Modified files: /phpdoc/en/language control-structures.xml Log: link to get_included_files, user note hint http://cvs.php.net/viewcvs.cgi/phpdoc/en/language/control-structures.xml?r1=1.130r2=1.131diff_format=u Index: phpdoc/en/language/control-structures.xml diff -u phpdoc/en/language/control-structures.xml:1.130 phpdoc/en/language/control-structures.xml:1.131 --- phpdoc/en/language/control-structures.xml:1.130 Tue Nov 29 21:27:09 2005 +++ phpdoc/en/language/control-structures.xml Sun Feb 12 19:52:23 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.130 $ -- +!-- $Revision: 1.131 $ -- chapter id=language.control-structures titleControl Structures/title @@ -1274,8 +1274,8 @@ simpara See also functioninclude/function, functionrequire_once/function, -functioninclude_once/function, functioneval/function, -functionfile/function, functionreadfile/function, +functioninclude_once/function, functionget_included_files/function, +functioneval/function, functionfile/function, functionreadfile/function, functionvirtual/function and link linkend=ini.include-pathinclude_path/link. /simpara /sect1 @@ -1619,8 +1619,8 @@ simpara See also functionrequire/function, functionrequire_once/function, -functioninclude_once/function, functionreadfile/function, -functionvirtual/function, and +functioninclude_once/function, functionget_included_files/function, +functionreadfile/function, functionvirtual/function, and link linkend=ini.include-pathinclude_path/link. /simpara /sect1
[PHP-DOC] cvs: phpdoc /en/reference/fdf/functions fdf-get-file.xml fdf-next-field-name.xml fdf-set-file.xml
betzSun Feb 12 20:56:42 2006 UTC Modified files: /phpdoc/en/reference/fdf/functions fdf-get-file.xml fdf-next-field-name.xml fdf-set-file.xml Log: example correction, user hintmisspelled function name, fdf_enum_fields does not exist http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/fdf/functions/fdf-get-file.xml?r1=1.3r2=1.4diff_format=u Index: phpdoc/en/reference/fdf/functions/fdf-get-file.xml diff -u phpdoc/en/reference/fdf/functions/fdf-get-file.xml:1.3 phpdoc/en/reference/fdf/functions/fdf-get-file.xml:1.4 --- phpdoc/en/reference/fdf/functions/fdf-get-file.xml:1.3 Mon Oct 21 20:57:18 2002 +++ phpdoc/en/reference/fdf/functions/fdf-get-file.xml Sun Feb 12 20:56:42 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.3 $ -- +!-- $Revision: 1.4 $ -- !-- splitted from ./en/functions/fdf.xml, last change in rev 1.2 -- refentry id=function.fdf-get-file refnamediv @@ -13,7 +13,7 @@ methodparamtyperesource/typeparameterfdf_document/parameter/methodparam /methodsynopsis para - The functionfdf_set_file/function returns the value + The functionfdf_get_file/function returns the value of the /F key. /para para http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/fdf/functions/fdf-next-field-name.xml?r1=1.6r2=1.7diff_format=u Index: phpdoc/en/reference/fdf/functions/fdf-next-field-name.xml diff -u phpdoc/en/reference/fdf/functions/fdf-next-field-name.xml:1.6 phpdoc/en/reference/fdf/functions/fdf-next-field-name.xml:1.7 --- phpdoc/en/reference/fdf/functions/fdf-next-field-name.xml:1.6 Thu Jan 15 12:42:20 2004 +++ phpdoc/en/reference/fdf/functions/fdf-next-field-name.xml Sun Feb 12 20:56:42 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- splitted from ./en/functions/fdf.xml, last change in rev 1.2 -- refentry id=function.fdf-next-field-name refnamediv @@ -37,8 +37,7 @@ /example /para para - See also functionfdf_enum_fields/function and - functionfdf_get_value/function. + See also functionfdf_get_value/function. /para /refsect1 /refentry http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/fdf/functions/fdf-set-file.xml?r1=1.4r2=1.5diff_format=u Index: phpdoc/en/reference/fdf/functions/fdf-set-file.xml diff -u phpdoc/en/reference/fdf/functions/fdf-set-file.xml:1.4 phpdoc/en/reference/fdf/functions/fdf-set-file.xml:1.5 --- phpdoc/en/reference/fdf/functions/fdf-set-file.xml:1.4 Sat Aug 16 17:06:53 2003 +++ phpdoc/en/reference/fdf/functions/fdf-set-file.xml Sun Feb 12 20:56:42 2006 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.4 $ -- +!-- $Revision: 1.5 $ -- !-- splitted from ./en/functions/fdf.xml, last change in rev 1.2 -- refentry id=function.fdf-set-file refnamediv @@ -37,16 +37,16 @@ $fdf = fdf_create(); /* set field foo to value bar */ - $fdf_set_value($fdf, foo, bar); + fdf_set_value($fdf, foo, bar); /* tell client to display FDF data using fdf_form.pdf */ fdf_set_file($fdf, http://www.example.com/fdf_form.pdf;); /* output fdf */ - fdf_save(); + fdf_save($fdf); /* clean up */ - fdf_close(); + fdf_close($fdf); ? ]] /programlisting
Re: [PHP-DOC] one parameter for two options!?
Jan Pieper wrote: http://www.php.net/printer-set-option [...] PRINTER_FORMAT_LETTER: specifies standard letter format (8 1/2- by 11-inches). PRINTER_FORMAT_LETTER: specifies standard legal format (8 1/2- by 14-inches). [...] mistake!? Jan Pieper Please open a bug report at bugs.php.net category Documentation problem. Thanks Friedhelm
Re: [PHP-DOC] cvs: phpdoc /en/chapters tutorial.xml
Serdar Soydemir wrote: tpugThu Jan 12 16:10:30 2006 UTC Modified files: /phpdoc/en/chapters tutorial.xml Log: You committed your translation to the english tree of the manual. Please revert, thanks. Friedhelm
Re: [PHP-DOC] #35432 [Asn]: make fails with PDO and MySQL5
Hi Goba, Curt Zirzow wrote: On Thu, Dec 01, 2005 at 08:45:34PM +0100, Gabor Hojtsy wrote: I almost went as far as creating a whole document dedicated to the installation of PDO, but wasn't sure where it would go. [1] http://livedocs.zirzow.dyndns.org/index.php?l=enq=ref.pdo [2] http://livedocs.zirzow.dyndns.org/index.php?l=enq=ref.pdo-sqlite Curt. Curt, this looks nice. What is the thing you are not sure about? I was considering making a driver-install.xml page inside pdo that would explain how to install the drivers. Like ordering of the extensions in php.ini, shared vs static installation and also cross reference the pecl.install page. So instead of having a reftitle.install; in all the driver pages, since most of them will be the same except sqlite, just cover all the procedures in that page. Now that I typed that, a install section per driver sounds like the best solution. Well, otherwise readers would not find it... Unless this driver-install page is linked from all the install pages. I prefer a install section per driver. I myelf installed pdo and some drivers yesterday (the first time) with php 5.1.1. for an ISP and I expected the install instructions for the drivers in their corresponding driver-specific page. IMHO, this seems to be the most user friendly solution. Friedhelm
Re: [PHP-DOC] Manual Credits/Contributors
Hi all, Gabor Hojtsy wrote: I have an important exam tomorrow, so I will only be able to add my opinion later this week (probably weekend). This is high priority on my TODO however, not forgotten! Goba Jakub Vrana wrote: Sean Coates wrote: I don't want to start a huge campaign of people who are in/out, but I _do_ think we should update this list, at least yearly. I propose this list to the cover: Mehdi Achour Friedhelm Betz (+) Sean Coates Antony Dovgal Nuno Lopes (+) Aidan Lister Philip Olson Jakub Vrana I don't know about much about Aidan, but I am strong + 1 to add Sean ASAP. I also like the idea of an infrastructure category to give credits for Derick and Hartmut (and maybe others I can't think of right now). Friedhelm
Re: [PHP-DOC] Documenting a pecl extension, but...
Hi Michael, Hi, if I ever come around to properly document my pecl extension, I wonder how I would need to proceed as there already is reference/http/reference.xml? I'd appreciate any hints and suggestions! hui, I think name it like your package name: pecl_http. But, thats ugly ;-) Anyway, this is somewhat of common sense for the docs, to name pecl packages like their package names, AFAIR. And as pecl package http as documentation end point is not possible, IMHO. Hint: to start documenting your extension you might want to use http://cvs.php.net/phpdoc/scripts/xml_proto.php for generating doc stubs. Friedhelm
Re: [PHP-DOC] Documenting a pecl extension, but...
Gabor Hojtsy wrote: hui, I think name it like your package name: pecl_http. But, thats ugly ;-) Yeah, *ugly* The extension name is actually http, the package has just been named pecl_http because there already was a HTTP package in PEAR. Ok, since there is no actual http extension in PHP, and we use the http extension designation just to group some http related functions, what if we move these to the network functions (and pray that a network extension will not come around :), and let the http extension be documented under its real name: http? Plus we would link to the network functions documentation page on the new http extension page, so that people will still find built in http functionality. That would be the nicest solution ;-) In addition we need to adjust the shortcuts for the integrated http related functions, so e.g. php.net/headers points to the right place. Friedhelm
Re: [PHP-DOC] Translating PDO, Files Generated by xml_proto.php
Dan Scott wrote: Do you want me to remove the comment from the source files? I had just left it in because, well, that's what the xml_proto script put in, and I thought it was meant to direct other people writing documentation to the script. But if it's just annoying I'm happy to delete it. IMHO it is not annoying (at least me) and in doubt it can people direct to the script. +1 for keeping the comment in the script file. Friedhelm
Re: [PHP-DOC] Legal function names?
wechsler wrote: The page at http://www.php.net/manual/en/language.functions.php doesn't specify (as far as I can see) what constitutes a legal function name. On the other hand, http://www.php.net/manual/en/language.variables.php does contain a regexp specifying variable names. Could someone who knows the pattern specify it in the manual? Unfortunately I don't know it myself, or I'd add it in a note. Thanks, Richard Please report bugs at http://bugs.php.net Friedhelm
Re: [PHP-DOC] Request for clarification
Claus Conrad wrote: Dear documentation team, The install.txt in the Windows zip file and the page http://dk2.php.net/manual/da/configuration.php#configuration.file http://dk2.php.net/manual/da/configuration.php#configuration.file state that the location of php.ini is searched for, among others, using the environment variable ”PHPRC”. Could you please clarify in these two documents, if the environment variable should contain the path to the directory containing php.ini or the path to the file itself, including its name? Please, submit documentation bugs at http://bugs.php.net Regards Friedhelm
[PHP-DOC] #35146 [Opn-Bgs]: ErrorDocument 404
ID: 35146 Updated by: [EMAIL PROTECTED] Reported By: kingva at jy-trading dot com -Status: Open +Status: Bogus Bug Type: Documentation problem Operating System: FreeBSD PHP Version: Irrelevant New Comment: Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Due to the volume of reports we can not explain in detail here why your report is not a bug. The support channels will be able to provide an explanation for you. Thank you for your interest in PHP. The bug system is not the place to answer user questions. Please use the appropriate support options (mailinglists etc.) Friedhelm Previous Comments: [2005-11-08 02:41:16] kingva at jy-trading dot com Description: I made file .htaccess in the default directory,include following content: ErrorDocument 404 /404.php also I made a file:404.php, Reproduce code: --- 404.php: html head meta http-equiv=content-type content=text/html; charset=iso-8859-1 titletitle/title /head ?php $url=getenv(REQUEST_URI); $pos = strpos($url, '/'); $url = substr($url, $pos+1); $suggestedurl=DoRedirect($url); ? script language=JavaScript window.top.location=?php print($suggestedurl);?; /script Expected result: If the URL is not exist, We will get another url. Actual result: -- sometimes working well, sometimes not in the IE, But in the Firefox, it always working well. but on my local computer, it always working well. the actual address: www.winmag.nl you can test : www.winmag.nl/1265 you should get the article 1265, but sometimes not, maybe you get The page cannot be found, if you refresh in the IE. Maybe you get the article. I dont know what's the reason, Can you help me? -- Edit this bug report at http://bugs.php.net/?id=35146edit=1
Re: [PHP-DOC] cvs: phpdoc /en/reference/yaz configure.xml
Hello Adam, Adam Dickmeiss wrote: [...] + para + The PHP 5.0.5 Win32 zip includes a too old version of + filenameyaz.dll/filename (version 1.9.1 required version 2.0.13). + If that's the case use the filenameyaz.dll/filename from a newer + ulink url=url.yaz.ftp.win32;YAZ WIN32 install/ulink. + /para + /warning + + para + On windows, copy filenameyaz.dll/filename to a directory in your + varnamePATH/varname environment + (filename class=directoryc:\winnt\system32/filename or + filename class=directoryc:\windows\system32/filename). /para AFAIR we decided to encourage people NOT to copy support dlls to the system folders. We should be consistent (some parts of the manual are not) and advice people to put this dlls in the main folder, e.g.: c:\php and add this directory to their path environment variable. Regards Friedhelm
Re: [PHP-DOC] cvs: phpdoc /en/reference/exif/functions exif-read-data.xml
Oliver Albers wrote: simpThu Oct 6 13:05:56 2005 EDT Modified files: /phpdoc/en/reference/exif/functions exif-read-data.xml Log: Bug #34764: returns mixed This bug is bogus IMHO, in section Return values it is mentioned that on failure the function return false. [...] methodsynopsis - typearray/typemethodnameexif_read_data/methodname + typemixed/typemethodnameexif_read_data/methodname methodparamtypestring/typeparameterfilename/parameter/methodparam methodparam choice=opttypestring/typeparametersections/parameter/methodparam methodparam choice=opttypebool/typeparameterarrays/parameter/methodparam AFAIR we had the decision, that the prototype should be the main type returned on success. mixed would be, returns eg. array or string and false on failure. Please revert your commit and mark that bug bogus. Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/mysql/functions mysql-fetch-field.xml
betzWed Oct 5 09:48:28 2005 EDT
Modified files:
/phpdoc/en/reference/mysql/functionsmysql-fetch-field.xml
Log:
document def, user notes;correct example, localhost:port is bogus
http://cvs.php.net/diff.php/phpdoc/en/reference/mysql/functions/mysql-fetch-field.xml?r1=1.13r2=1.14ty=u
Index: phpdoc/en/reference/mysql/functions/mysql-fetch-field.xml
diff -u phpdoc/en/reference/mysql/functions/mysql-fetch-field.xml:1.13
phpdoc/en/reference/mysql/functions/mysql-fetch-field.xml:1.14
--- phpdoc/en/reference/mysql/functions/mysql-fetch-field.xml:1.13 Thu Mar
31 02:47:25 2005
+++ phpdoc/en/reference/mysql/functions/mysql-fetch-field.xml Wed Oct 5
09:48:24 2005
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.13 $ --
+!-- $Revision: 1.14 $ --
refentry id=function.mysql-fetch-field
refnamediv
refnamemysql_fetch_field/refname
@@ -58,6 +58,11 @@
/listitem
listitem
simpara
+ def - default value of the column
+ /simpara
+/listitem
+listitem
+ simpara
max_length - maximum length of the column
/simpara
/listitem
@@ -118,7 +123,7 @@
programlisting role=php
![CDATA[
?php
-$conn = mysql_connect('localhost:3306', 'user', 'password');
+$conn = mysql_connect('localhost', 'mysql_user', 'mysql_password');
if (!$conn) {
die('Could not connect: ' . mysql_error());
}
@@ -145,6 +150,7 @@
primary_key: $meta-primary_key
table:$meta-table
type: $meta-type
+default: $meta-def
unique_key: $meta-unique_key
unsigned: $meta-unsigned
zerofill: $meta-zerofill
Re: [PHP-DOC] Critical files in translation
Jakub Vrana wrote: Sean Coates wrote: I just had a short discussion with Sean about critical files in translations of the manual and he suggested I'd bother all of you with the issue. ;) Livedocs handle this pretty well IMHO. It shows the translation and then: The translation of this file is outdated. Click here to read this file in english. Thats nice, but does not solve any problems in the near future. SO, my solution is to add an entity that says something along the lines of This documentation is critically outdated; see the English translation. And have a revcheck-like script determine which files are POTENTIALLY outdated. Then, a user can stick note.outdated; into any files that he has personally reviewed and considers out of date. That's not going to work. If there's a lack of translators then there will be also lack of note-stickers. Thats a valid concern, but we loose nothing, we just can gain something. This gives at least the possibility to act if some of the translators want to do. If they want to do something, we give them the possibility. Thats better than nothing ;-) Friedhelm
[PHP-DOC] #32728 [Fbk]: new build system for win32 not documented
ID: 32728 Updated by: [EMAIL PROTECTED] Reported By: holliwell at gmx dot net Status: Feedback Bug Type: Documentation problem Operating System: windows PHP Version: Irrelevant Assigned To: nlopess New Comment: No it's too vague, at least for me ;-) quote and Visual Studio (6 or .Net), either a free (sdk, whatever) or a commercial version. /quote So, what is whatever? What do I need to build *php5*? Commercial vc6, Vc7, or is there a possibility to build with a free one, and if so what tools/free sdk's are required? Another quote from the online version: To compile and build PHP you need a Microsoft Development Environment. Microsoft Visual C++ 6.0 is recommended, although .NET versions will also work. Is vc6 sufficient to build php5 with the new build system? Don't get me wrong, but I think this sort of questions should be clear from the requirements section. Answers for this questions are not covered by the current requirement section. Thanks Friedhelm Previous Comments: [2005-10-04 21:04:04] [EMAIL PROTECTED] isn't http://php.net/install.windows.building#install.windows.building.requirement enough?? you only need a windows system :) and Visual Studio (6 or .Net), either a free (sdk, whatever) or a commercial version. [2005-10-04 13:28:21] holliwell at gmx dot net Nuno, thanks for putting that together. It would be helpful, to have a section about requirements which answers the question: What tools/software/updates/ etc. do I need to build php5 with the new build system? I remember, Wez has posted requirements some time ago to internals. A requirements section would be definitly helpful. Friedhelm [2005-09-25 12:30:42] [EMAIL PROTECTED] I think everything is now documented. Please read it (after the next manual build) and let me know of any errors/omissions. [2005-04-16 17:58:34] holliwell at gmx dot net Description: The new configure-like build system for win32 is not covered by the docs. I think we need detailed documentation about how to build php from source on win32. Important, as of php5 the supplied .dsp-Files for VC6 are not well maintainded. -- Edit this bug report at http://bugs.php.net/?id=32728edit=1
Re: [PHP-DOC] classes parent::parent
Stefan Varga wrote:
Hi,
I searched thru the documentation and can not find a way to call a
object's parent's parent method. I do not want to call the direct
parent method. Let me demonstrate on an example.
class A {
function show() {
echo A;
general handling
}
}
class B extends A {
function show() {
echo B;
special handling for B;
parent::show();
}
}
class C extends B {
function show() {
echo C;
special handling C;
parent::parent::show();
}
}
The call parent::parent::show(); in C does not work.
Please, ask support questions at one of the available mailinglists:
http://www.php.net/mailing-lists.php
Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/mysql constants.xml
betzMon Oct 3 06:34:29 2005 EDT Modified files: /phpdoc/en/reference/mysql constants.xml Log: id for the client flags table, allows direct linking http://cvs.php.net/diff.php/phpdoc/en/reference/mysql/constants.xml?r1=1.7r2=1.8ty=u Index: phpdoc/en/reference/mysql/constants.xml diff -u phpdoc/en/reference/mysql/constants.xml:1.7 phpdoc/en/reference/mysql/constants.xml:1.8 --- phpdoc/en/reference/mysql/constants.xml:1.7 Thu Aug 19 09:13:34 2004 +++ phpdoc/en/reference/mysql/constants.xml Mon Oct 3 06:34:29 2005 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.7 $ -- +!-- $Revision: 1.8 $ -- section id=mysql.constants reftitle.constants; extension.constants; @@ -7,7 +7,7 @@ Since PHP 4.3.0 it is possible to specify additional client flags for the functionmysql_connect/function and functionmysql_pconnect/function functions. The following constants are defined: - table + table id=mysql.client-flags titleMySQL client constants/title tgroup cols=2 thead
[PHP-DOC] cvs: phpdoc /en/reference/mysql/functions mysql-connect.xml
betzMon Oct 3 06:37:10 2005 EDT
Modified files:
/phpdoc/en/reference/mysql/functionsmysql-connect.xml
Log:
more examples for connecting with different syntax, link to client flags
table, link to ini-setting
http://cvs.php.net/diff.php/phpdoc/en/reference/mysql/functions/mysql-connect.xml?r1=1.16r2=1.17ty=u
Index: phpdoc/en/reference/mysql/functions/mysql-connect.xml
diff -u phpdoc/en/reference/mysql/functions/mysql-connect.xml:1.16
phpdoc/en/reference/mysql/functions/mysql-connect.xml:1.17
--- phpdoc/en/reference/mysql/functions/mysql-connect.xml:1.16 Mon Jun 20
23:05:09 2005
+++ phpdoc/en/reference/mysql/functions/mysql-connect.xml Mon Oct 3
06:37:09 2005
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.16 $ --
+!-- $Revision: 1.17 $ --
refentry id=function.mysql-connect
refnamediv
refnamemysql_connect/refname
@@ -80,6 +80,7 @@
constantMYSQL_CLIENT_COMPRESS/constant,
constantMYSQL_CLIENT_IGNORE_SPACE/constant or
constantMYSQL_CLIENT_INTERACTIVE/constant.
+ Read the section about xref linkend=mysql.client-flags / for
further information.
/para
/listitem
/varlistentry
@@ -156,6 +157,61 @@
/programlisting
/example
/para
+ para
+ example
+titlefunctionmysql_connect/functionexample using
literalhostname:port/literal syntax/title
+programlisting role=php
+![CDATA[
+?php
+// we connect to example.com and port 3307
+$link = mysql_connect('example.com:3307', 'mysql_user', 'mysql_password');
+if (!$link) {
+die('Could not connect: ' . mysql_error());
+}
+echo 'Connected successfully';
+mysql_close($link);
+
+// we connect to localhost at port 3307
+$link = mysql_connect('127.0.0.1:3307', 'mysql_user', 'mysql_password');
+if (!$link) {
+die('Could not connect: ' . mysql_error());
+}
+echo 'Connected successfully';
+mysql_close($link);
+?
+]]
+/programlisting
+ /example
+ /para
+ para
+ example
+titlefunctionmysql_connect/functionexample using :/path/to/socket
syntax/title
+programlisting role=php
+![CDATA[
+?php
+// we connect to localhost and socket e.g. /tmp/mysql.sock
+
+//variant 1: ommit localhost
+$link = mysql_connect('/tmp/mysql', 'mysql_user', 'mysql_password');
+if (!$link) {
+die('Could not connect: ' . mysql_error());
+}
+echo 'Connected successfully';
+mysql_close($link);
+
+
+// variant 2: with localhost
+$link = mysql_connect('localhost:/tmp/mysql.sock', 'mysql_user',
'mysql_password');
+if (!$link) {
+die('Could not connect: ' . mysql_error());
+}
+echo 'Connected successfully';
+mysql_close($link);
+?
+]]
+/programlisting
+ /example
+ /para
/refsect1
refsect1 role=notes
@@ -168,7 +224,7 @@
Windows). If you want to use TCP/IP, use quot;127.0.0.1quot;
instead of quot;localhostquot;. If the MySQL client library tries to
connect to the wrong local socket, you should set the correct path as
-mysql.default_host in your PHP configuration and leave the server field
+xref linkend= ini.mysql.default-host / in your PHP configuration and
leave the server field
blank.
/para
/note
[PHP-DOC] #34715 [Opn]: Apache 2 prefork MPM on Windows?
ID: 34715 Updated by: [EMAIL PROTECTED] Reported By: ovdspek at liacs dot nl Status: Open Bug Type: Documentation problem Operating System: Windows PHP Version: Irrelevant New Comment: You can compile Apache2 on Windows with prefork mpm Previous Comments: [2005-10-03 12:49:21] ovdspek at liacs dot nl Oops, some typos: Is this not correct and is there a prefork version of Apache 2 for Windows? [2005-10-03 12:44:48] ovdspek at liacs dot nl I meant that it applies to anything but Windows. I assumed there's only one MPM for Windows (can't find any other binary on the Apache site). Is this not correct and is there are preform version of Apache 2 for Windows? [2005-10-03 12:01:13] [EMAIL PROTECTED] It's indeed non windows specific, but as the default MPM on windows is threaded, the warning suits here just fine. [2005-10-03 11:51:32] ovdspek at liacs dot nl Description: http://nl3.php.net/manual/en/install.windows.apache2.php says: We do not recommend using a threaded MPM in production with Apache2. Use the prefork MPM instead, or use Apache1. For information on why, read the related FAQ entry on using Apache2 with a threaded MPM Isn't that non-Windows specific? What is it doing on the Windows page? -- Edit this bug report at http://bugs.php.net/?id=34715edit=1
[PHP-DOC] cvs: phpdoc /en/reference/funchand/functions register-tick-function.xml
betzMon Oct 3 07:27:48 2005 EDT Modified files: /phpdoc/en/reference/funchand/functions register-tick-function.xml Log: warning about ZTS, declare is not a function http://cvs.php.net/diff.php/phpdoc/en/reference/funchand/functions/register-tick-function.xml?r1=1.9r2=1.10ty=u Index: phpdoc/en/reference/funchand/functions/register-tick-function.xml diff -u phpdoc/en/reference/funchand/functions/register-tick-function.xml:1.9 phpdoc/en/reference/funchand/functions/register-tick-function.xml:1.10 --- phpdoc/en/reference/funchand/functions/register-tick-function.xml:1.9 Thu Jun 23 12:53:27 2005 +++ phpdoc/en/reference/funchand/functions/register-tick-function.xml Mon Oct 3 07:27:47 2005 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.9 $ -- +!-- $Revision: 1.10 $ -- !-- splitted from ./en/functions/funchand.xml, last change in rev 1.12 -- refentry id=function.register-tick-function refnamediv @@ -19,7 +19,7 @@ simpara Registers the function named by parameterfunc/parameter to be executed when a link - linkend=control-structures.declaretick/link is + linkend=control-structures.declare.tickstick/link is called. Also, you may pass an array consisting of an object and a method as the parameterfunc/parameter. /simpara @@ -40,8 +40,15 @@ /programlisting /example /para +warning + simpara + functionregister_tick_function/function should not be used with + threaded webserver modules. Ticks are not working in ZTS mode and may + crash your webserver. + /simpara +/warning para - See also functiondeclare/function and + See also link linkend=control-structures.declaredeclare/link and functionunregister_tick_function/function. /para /refsect1
Re: [PHP-DOC] 2 Documentation issues (online version, german)
Der Ernst wrote: Hello PHP Documentation Team I noticed 2 different issues in the documentation (of which I use the German online version): 1. Encoding of pages: The encoding for the documentation text and the user notes are different. This is very obvious at the strtr() function page http://php.benscom.com/manual/de/function.strtr.php: In normal mode (utf-8 encoding) all special characters in the user notes are wrong. If I change IE's encoding setting manually to Western European (ISO or Windows), the user notes will be displayed correctly (more or less...), but non-ASCII characters in the main text are wrong then. This might be solveable by adding add-charset=UTF-8 to the form tag of the add user note page. 2. German documentation of trim() function: http://php.benscom.com/manual/de/function.trim.php In the german version the second attribute is not documented. Manually choosing the english documentation shows a much more detailled documentation of the trim() function. Thanks for your attention! Markus Ernst Please, file a bug report at http://bugs.php.net. This will help us definitly to track this issues. Thanks Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions fgets.xml
betzFri Sep 16 07:13:47 2005 EDT
Modified files:
/phpdoc/en/reference/filesystem/functions fgets.xml
Log:
prevent infinite loop, user notes
http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/fgets.xml?r1=1.13r2=1.14ty=u
Index: phpdoc/en/reference/filesystem/functions/fgets.xml
diff -u phpdoc/en/reference/filesystem/functions/fgets.xml:1.13
phpdoc/en/reference/filesystem/functions/fgets.xml:1.14
--- phpdoc/en/reference/filesystem/functions/fgets.xml:1.13 Tue Jul 20
06:25:33 2004
+++ phpdoc/en/reference/filesystem/functions/fgets.xml Fri Sep 16 07:13:44 2005
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.13 $ --
+!-- $Revision: 1.14 $ --
!-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 --
refentry id=function.fgets
refnamediv
@@ -40,12 +40,14 @@
programlisting role=php
![CDATA[
?php
-$handle = fopen(/tmp/inputfile.txt, r);
-while (!feof($handle)) {
-$buffer = fgets($handle, 4096);
-echo $buffer;
+$handle = @fopen(/tmp/inputfile.txt, r);
+if ($handle) {
+while (!feof($handle)) {
+$buffer = fgets($handle, 4096);
+echo $buffer;
+}
+fclose($handle);
}
-fclose($handle);
?
]]
/programlisting
[PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions fgets.xml
betzFri Sep 16 07:30:17 2005 EDT Modified files: /phpdoc/en/reference/filesystem/functions fgets.xml Log: see also fgetss http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/fgets.xml?r1=1.14r2=1.15ty=u Index: phpdoc/en/reference/filesystem/functions/fgets.xml diff -u phpdoc/en/reference/filesystem/functions/fgets.xml:1.14 phpdoc/en/reference/filesystem/functions/fgets.xml:1.15 --- phpdoc/en/reference/filesystem/functions/fgets.xml:1.14 Fri Sep 16 07:13:44 2005 +++ phpdoc/en/reference/filesystem/functions/fgets.xml Fri Sep 16 07:30:14 2005 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.14 $ -- +!-- $Revision: 1.15 $ -- !-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 -- refentry id=function.fgets refnamediv @@ -72,7 +72,8 @@ /note note.line-endings; para - See also functionfread/function, + See also functionfgetss/function + functionfread/function, functionfgetc/function, functionstream_get_line/function, functionfopen/function,
[PHP-DOC] cvs: phpdoc /scripts missing-entities.php.in
betzThu Sep 15 04:16:46 2005 EDT
Modified files:
/phpdoc/scripts missing-entities.php.in
Log:
support for xreflabel, avoids warnings like xref on para not supported
missing-ids.xml is back iin entities/ (see rev 1.17)
http://cvs.php.net/diff.php/phpdoc/scripts/missing-entities.php.in?r1=1.19r2=1.20ty=u
Index: phpdoc/scripts/missing-entities.php.in
diff -u phpdoc/scripts/missing-entities.php.in:1.19
phpdoc/scripts/missing-entities.php.in:1.20
--- phpdoc/scripts/missing-entities.php.in:1.19 Sun Aug 21 12:27:08 2005
+++ phpdoc/scripts/missing-entities.php.in Thu Sep 15 04:16:45 2005
@@ -17,7 +17,7 @@
| Gabor Hojtsy [EMAIL PROTECTED] |
+--+
- $Id: missing-entities.php.in,v 1.19 2005/08/21 16:27:08 goba Exp $
+ $Id: missing-entities.php.in,v 1.20 2005/09/15 08:16:45 betz Exp $
*/
set_time_limit(0);
@@ -93,7 +93,9 @@
// missing ID found
else if (strpos($line, non-existent) !== FALSE) {
-$missing_ids[] = preg_replace(!^.* ID !, para id=, $line) .
/para\n;
+ preg_match('!(?=ID.).+!', $line, $id);
+$missing_ids[] = para id= . $id[0] . xreflabel= . $id[0] .
/para\n;
+$missing_ids_display[] = id= . $id[0] . \n;
}
}
@@ -105,6 +107,10 @@
sort($missing_ids);
sort($missing_entities);
+// missing ids for display
+$missing_ids_display=array_unique($missing_ids_display);
+sort($missing_ids_display);
+
// Write out missing entities to file
foreach ($missing_entities as $ent) {
fwrite($ment, $ent);
@@ -136,9 +142,9 @@
echo * No missing entities were found\n;
}
-echo \nCreated file: @LANGDIR@/missing-ids.xml\n;
-if (!empty($missing_ids)) {
-foreach ($missing_ids as $k = $v) {
+echo \nCreated file: entities/missing-ids.xml\n;
+if (!empty($missing_ids_display)) {
+foreach ($missing_ids_display as $k = $v) {
echo * . preg_replace('@[\s]+@', ' ', $v) . \n;
}
} else {
Re: [PHP-DOC] build failure [de]
Gabor Hojtsy wrote: OK, why display the para extra, while you only need to see the missing IDs themselfs? Thanks for the hint. Otherwise if this works fine, I am all for having it comitted. As I can tell it works, just comitted. Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/session_pgsql/functions session-pgsql-reset.xml
betzThu Sep 15 04:30:24 2005 EDT Modified files: /phpdoc/en/reference/session_pgsql/functions session-pgsql-reset.xml Log: servers is correct, there can be more than one database server http://cvs.php.net/diff.php/phpdoc/en/reference/session_pgsql/functions/session-pgsql-reset.xml?r1=1.2r2=1.3ty=u Index: phpdoc/en/reference/session_pgsql/functions/session-pgsql-reset.xml diff -u phpdoc/en/reference/session_pgsql/functions/session-pgsql-reset.xml:1.2 phpdoc/en/reference/session_pgsql/functions/session-pgsql-reset.xml:1.3 --- phpdoc/en/reference/session_pgsql/functions/session-pgsql-reset.xml:1.2 Fri Sep 9 21:00:12 2005 +++ phpdoc/en/reference/session_pgsql/functions/session-pgsql-reset.xml Thu Sep 15 04:30:23 2005 @@ -1,10 +1,10 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- !-- Generated by xml_proto.php v2.2. Found in /scripts directory of phpdoc. -- refentry id=function.session-pgsql-reset refnamediv refnamesession_pgsql_reset/refname - refpurposeReset connection to session database server/refpurpose + refpurposeReset connection to session database servers/refpurpose /refnamediv refsect1 role=description reftitle.description; @@ -13,7 +13,7 @@ void/ /methodsynopsis para - Reset the connection to the session database server. + Reset the connection to the session database servers. /para /refsect1
[PHP-DOC] cvs: phpdoc /en/reference/session_pgsql/functions session-pgsql-status.xml
betzThu Sep 15 04:31:06 2005 EDT Modified files: /phpdoc/en/reference/session_pgsql/functions session-pgsql-status.xml Log: not experimental http://cvs.php.net/diff.php/phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml?r1=1.2r2=1.3ty=u Index: phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml diff -u phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml:1.2 phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml:1.3 --- phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml:1.2 Thu Sep 8 14:24:45 2005 +++ phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml Thu Sep 15 04:31:06 2005 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- !-- splitted from ./en/functions/session-pgsql.xml, last change in rev 1.2 -- refentry id=function.session-pgsql-status refnamediv @@ -13,7 +13,6 @@ typearray/typemethodnamesession_pgsql_status/methodname void/ /methodsynopsis - warn.experimental.func; warn.undocumented.func; /refsect1 /refentry
[PHP-DOC] cvs: phpdoc /en/reference/session_pgsql reference.xml
betzThu Sep 15 04:32:03 2005 EDT Modified files: /phpdoc/en/reference/session_pgsql reference.xml Log: More info from the README file in sources http://cvs.php.net/diff.php/phpdoc/en/reference/session_pgsql/reference.xml?r1=1.1r2=1.2ty=u Index: phpdoc/en/reference/session_pgsql/reference.xml diff -u phpdoc/en/reference/session_pgsql/reference.xml:1.1 phpdoc/en/reference/session_pgsql/reference.xml:1.2 --- phpdoc/en/reference/session_pgsql/reference.xml:1.1 Thu Sep 8 12:03:15 2005 +++ phpdoc/en/reference/session_pgsql/reference.xml Thu Sep 15 04:32:02 2005 @@ -1,8 +1,7 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.1 $ -- +!-- $Revision: 1.2 $ -- !-- Purpose: basic.session -- !-- Membership: pecl, external -- -!-- State: experimental-- !-- Author: Yasuo Ohgaki [EMAIL PROTECTED] -- reference id=ref.session-pgsql titlePostgreSQL Session Save Handler/title @@ -11,29 +10,41 @@ partintro section id=session-pgsql.intro reftitle.intro; -warn.experimental; note.no-windows.extension; para - This module provide additional session save handler for session module - using PostgreSQL as a storage. literaluser/literal session save - handler may be used, but this module is written in C. Therefore, this - module is roughly 2 times faster than save handler written in PHP script. + This module provides an additional session save handler for the + link linkend=ref.sessionsession/link + module using ulink url=url.pgsql;PostgreSQL/ulinkPostgreSQL as a + storage system. A literaluser/literal session save handler may be + used (function(session_set_save_handler/function, but this module is + written in C. Therefore, this module could be twice as fast, compared to + a session save handler written in PHP. /para para - Fail-over and load balance is planned to be implemented, but they are not - available now. -/para -note - simpara - There will be functions for this module, but it is not available now. - /simpara -/note + Session PgSQL is designed to scale any size of web sites and offers some + advanced features: + simplelist + membersession tables are created automatically/member + memberautomatic session table vacuum/member + memberbetter garbage collection/member + membermultiple PostgreSQL servers support/member + memberautomatic database server failover (switching)/member + member + automatic database server load balancing if there are multiple + PostgreSQL servers. + /member + membershort circuit UPDATE/member + /simplelist +/para /section section id=session-pgsql.requirements reftitle.required; para - You need at least PHP 4.1, PostgreSQL 7.1 and MM 1.1.3 + You need at least PHP gt;= 4.3.0, and PostgreSQL gt;=7.2.0 as database + server. literallibpq/literal that comes with PostgreSQL 7.2.0 or + later (and header files to build) and ulink url=url.mm;libmm/ulink + (and header files). /para /section @@ -41,6 +52,58 @@ reference.session-pgsql.ini; + section id=session-pgsql.tables +titleTable definitions/title +paraSession table definition + programlisting role=sql +![CDATA[ +CREATE TABLE php_session ( + sess_idtext, + sess_name text, + sess_data text, + sess_created integer, + sess_modified integer, + sess_expireinteger, + sess_addr_created text, + sess_addr_modified text, + sess_counter integer, + sess_error integer, + sess_warning integer, + sess_noticeinteger, + sess_err_message text, + sess_customtext +); + +CREATE INDEX php_session_idx ON php_session USING BTREE (sess_id); +]] + /programlisting +/para +warning + para + If you use literalHASH/literal for literalINDEX/literal, you'll + have a deadlock problem when the server load is + emphasisvery/emphasis high. Even if it's unlikely to have a deadlock + under normal operation, it can occur. emphasisDo not use + literalHASH/literal for literalINDEX/literal/emphasis. + /para +/warning +para + You may change the session table as long as all fields are defined. +/para +para + Application variables table definition + programlisting role=sql +![CDATA[ +CREATE TABLE php_app_vars ( + app_modified integer, + app_name text, + app_vars text +); +]] + /programlisting +/para + /section + section id=session-pgsql.contact titleContact Information/title
[PHP-DOC] cvs: phpdoc /en/reference/satellite .cvsignore reference.xml /en/reference/satellite/functions orbitenum.xml orbitobject.xml orbitstruct.xml satellite-caught-exception.xml satellite-excepti
betzThu Sep 15 05:02:29 2005 EDT
Added files:
/phpdoc/en/reference/satellite .cvsignore reference.xml
/phpdoc/en/reference/satellite/functionsorbitenum.xml
orbitobject.xml
orbitstruct.xml
satellite-caught-exception.xml
satellite-exception-id.xml
satellite-exception-value.xml
satellite-get-repository-id.xml
satellite-load-idl.xml
satellite-object-to-string.xml
Log:
move satellite from peardoc to phpdoc
http://cvs.php.net/co.php/phpdoc/en/reference/satellite/.cvsignore?r=1.1p=1
Index: phpdoc/en/reference/satellite/.cvsignore
+++ phpdoc/en/reference/satellite/.cvsignore
functions.xml
http://cvs.php.net/co.php/phpdoc/en/reference/satellite/reference.xml?r=1.1p=1
Index: phpdoc/en/reference/satellite/reference.xml
+++ phpdoc/en/reference/satellite/reference.xml
?xml version=1.0 encoding=iso-8859-1?
!-- $Revision: 1.1 $ --
!-- State: deprecated --
!-- Author: David Eriksson [EMAIL PROTECTED] --
reference id=ref.satellite
titleSatellite CORBA client extension [deprecated]/title
titleabbrevSatellite/titleabbrev
partintro
section id=satellite.intro
reftitle.intro;
warn.experimental;
note.no-windows.extension;
para
Satellite is deprecated. It is suggested that you use Universe
(ulink url=url.corba.universe;url.corba.universe;/ulink) and not
Satellite.
/para
para
The Satellite extension is used for accessing CORBA objects. You
will need to set the literalidl_directory=/literal entry in php.ini;
to a path where you store all IDL files you use.
/para
para
See the Satellite filenameREADME/filenamefile for details about
installing Satellite.
/para
/section
/partintro
reference.satellite.functions;
/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
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:../../../manual.ced
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
--
http://cvs.php.net/co.php/phpdoc/en/reference/satellite/functions/orbitenum.xml?r=1.1p=1
Index: phpdoc/en/reference/satellite/functions/orbitenum.xml
+++ phpdoc/en/reference/satellite/functions/orbitenum.xml
?xml version=1.0 encoding=iso-8859-1?
!-- $Revision: 1.1 $ --
!-- splitted from ./en/functions/satellite.xml, last change in rev 1.2 --
refentry id=function.orbitenum
refnamediv
refnameOrbitEnum/refname
refpurposeUse CORBA enums/refpurpose
/refnamediv
refsect1 role=description
reftitle.description;
methodsynopsis
typenew/typemethodnameOrbitEnum/methodname
methodparamtypestring/typeparameterid/parameter/methodparam
/methodsynopsis
warn.experimental.func;
para
This class represents the enumeration identified with the
parameterid/parameter parameter.
/para
/refsect1
refsect1 role=parameters
reftitle.parameters;
para
variablelist
varlistentry
termparameterid/parameter/term
listitem
para
Can be either the name of the enumeration (e.g MyEnum), or the full
repository id (e.g. IDL:MyEnum:1.0).
/para
/listitem
/varlistentry
/variablelist
/para
/refsect1
refsect1 role=examples
reftitle.examples;
para
example
titleSample IDL file/title
programlisting role=txt
![CDATA[
enum MyEnum {
a,b,c,d,e
};
]]
/programlisting
/example
/para
para
example
titlePHP code for accessing MyEnum/title
programlisting role=php
![CDATA[
?php
$enum = new OrbitEnum (MyEnum);
echo $enum-a; /* write 0 */
echo $enum-c; /* write 2 */
echo $enum-e; /* write 4 */
?
]]
/programlisting
/example
/para
/refsect1
/refentry
!-- 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
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:../../../../manual.ced
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
--
http://cvs.php.net/co.php/phpdoc/en/reference/satellite/functions/orbitobject.xml?r=1.1p=1
Index: phpdoc/en/reference/satellite/functions/orbitobject.xml
+++ phpdoc/en/reference/satellite/functions/orbitobject.xml
?xml version=1.0 encoding=iso-8859-1?
!-- $Revision: 1.1
Re: [PHP-DOC] build failure [de]
Gabor Hojtsy wrote:
Fine with me, but we should place missing; at top of missing-ids.xml
So the following should be the solution for this problem:
missing-ids.xml:
missing;
para id=ini.com.allow-dcom xreflabel=ini.com.allow-dcom/para
and put missing; in language-snippets.ent.
Benefit: linking to appendix missing-stuff with a short explanation is
working again ;-)
I actually meant that every xreflabel (so every link generated for
missing content) would include the translated version of the word
missing, so that even before clicked a user (an experienced user at
least) would know that it is not really benefical to click that link.
Sorry for the late response.
Entities in attribut values are not allowed.
See the attached patch against missing-entities.php.in for
xreflabel-support.
Friedhelm
Index: missing-entities.php.in
===
RCS file: /repository/phpdoc/scripts/missing-entities.php.in,v
retrieving revision 1.19
diff -u -r1.19 missing-entities.php.in
--- missing-entities.php.in 21 Aug 2005 16:27:08 - 1.19
+++ missing-entities.php.in 14 Sep 2005 18:44:45 -
@@ -93,7 +93,9 @@
// missing ID found
else if (strpos($line, non-existent) !== FALSE) {
-$missing_ids[] = preg_replace(!^.* ID !, para id=, $line) .
/para\n;
+ preg_match('!(?=ID.).+!', $line, $id);
+$missing_ids[] = para id= . $id[0] . xreflabel= . $id[0] .
/para\n;
+$missing_ids_display[]=para id= . $id[0] . /para\n;
}
}
@@ -105,6 +107,10 @@
sort($missing_ids);
sort($missing_entities);
+// missing ids for display
+$missing_ids_display=array_unique($missing_ids_display);
+sort($missing_ids_display);
+
// Write out missing entities to file
foreach ($missing_entities as $ent) {
fwrite($ment, $ent);
@@ -137,8 +143,8 @@
}
echo \nCreated file: @LANGDIR@/missing-ids.xml\n;
-if (!empty($missing_ids)) {
-foreach ($missing_ids as $k = $v) {
+if (!empty($missing_ids_display)) {
+foreach ($missing_ids_display as $k = $v) {
echo * . preg_replace('@[\s]+@', ' ', $v) . \n;
}
} else {
Re: [PHP-DOC] Übersetzungsteam Deutsch
[EMAIL PROTECTED] wrote: Hallo, ich würde gerne mitwirken das PHP-Handbuch auf Deutsch zu übersetzen. Es wäre sehr nett wenn ich Informationen darüber erhalten könnte. Mit freundlichen Grüßen Marcus Lehrmann Please contact the german translators: [EMAIL PROTECTED] Volunteers are very welcome! A good start is to read our howto: http://doc.php.net/php/dochowto/ Information for Translators http://doc.php.net/php/dochowto/chapter-translation.php Please ask further questions on [EMAIL PROTECTED] (and exclude [EMAIL PROTECTED]@php.net from the cc) Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/zlib reference.xml
betzTue Sep 13 18:39:35 2005 EDT Modified files: /phpdoc/en/reference/zlib reference.xml Log: rewording, usage of compression.zlib, link to compression wrappers http://cvs.php.net/diff.php/phpdoc/en/reference/zlib/reference.xml?r1=1.15r2=1.16ty=u Index: phpdoc/en/reference/zlib/reference.xml diff -u phpdoc/en/reference/zlib/reference.xml:1.15 phpdoc/en/reference/zlib/reference.xml:1.16 --- phpdoc/en/reference/zlib/reference.xml:1.15 Sun Sep 4 07:49:43 2005 +++ phpdoc/en/reference/zlib/reference.xml Tue Sep 13 18:39:34 2005 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.15 $ -- +!-- $Revision: 1.16 $ -- !-- Purpose: compression -- !-- Membership: bundled -- @@ -20,20 +20,21 @@ note para Version 4.0.4 introduced a fopen-wrapper for .gz-files, so that - you can use a special 'zlib:' URL to access compressed files - transparently using the normal f*() file access functions if you - prepend the filename or path with a 'zlib:' prefix when calling - functionfopen/function. + you can use a special filenamezlib:/filename URL to access + compressed files transparently using the normal f*() file access + functions if you prefix the filename or path with + filenamezlib:/filename when calling functionfopen/function. This + feature requires a C runtime library that provides the + literalfopencookie()/literal function. Up to now the GNU libc + seems to be the only library that provides this feature. /para para - In version 4.3.0, this special prefix has been changed to 'zlib://' - to prevent ambiguities with filenames containing ':'. - /para - para - This feature requires a C runtime library that provides the - literalfopencookie()/literal function. To my current - knowledge the GNU libc is the only library that provides - this feature. + In PHP 4.3.0, filenamezlib:/filename has been changed to + filenamecompress.zlib:///filename to prevent ambiguities with + filenames containing ':' characters. The + literalfopencookie()/literal function is not longer required. + More information is available in the section about + xref linkend=wrappers.compression /. /para /note /section
Re: [PHP-DOC] build failure [de]
Gabor Hojtsy wrote: The problem is the increased usage of xref. Previously authors were encouraged to use link to add internal links, which requires text content, so this was no problem. The adoption of xref lead to this problem. Should we avoid using xref? I don't think so that now it is an option. It is quite convinient in places like the extensions.xml file, where generated content is automatically translated with the titles, and this is the intention of using xref elsewhere too. Less work for translators to look up how exactly they translated some titles = more consistency in translations. +1, xref is a neet feature. 1. What would we put into para xreflabel=... in place of the dots in the missing-ids.xml file? The proper link-test? Sure, this depends on the content of the id=.. For the example para id=ini.com.allow-dcom this would become para id=ini.com.allow-dcom xreflabel=com.allow_dcom For ini stuff, this works because of some strict rules for naming. Otherwise we might not have this type of rule to generate a meaningful title. What if we do para id=ini.com.allow-dcom xreflabel=ini.com.allow-dcom (missing;) Where missing; is translated obviously. It would give some clue to users why clicking on that link leads to no content. :) Fine with me, but we should place missing; at top of missing-ids.xml So the following should be the solution for this problem: missing-ids.xml: missing; para id=ini.com.allow-dcom xreflabel=ini.com.allow-dcom/para and put missing; in language-snippets.ent. Benefit: linking to appendix missing-stuff with a short explanation is working again ;-) Friedhelm
[PHP-DOC] build failure [de]
Hi, The manual build of the de manual fails with following messages: sample: /usr/bin/openjade:/dat/dev/php/phpdoc/en/faq/com.xml:146:34:E: [xref auf para wird nicht unterstützt] [xref on para is not supported] The id xref is linking to, is missing in the de-tree, but present in the missing-ids.xml file: para id=ini.com.allow-dcom/para In the english file in question (faq/com.xml) xref is used like: xref linkend=ini.com.allow-dcom/ As this points to para id=ini.com.allow-dcom/para in missing-ids.xml for the de tree, obviously no link text can be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? Possibilities (other than updating the german manual ;-)): 1.) use xreflabel 2.) produce content for the para's in missing-ids.xml 3.) split the faq Any suggestions? I prefer 2.) or 3.) Thanks, Friedhelm
Re: [PHP-DOC] build failure [de]
Gabor Hojtsy wrote: [xref on para is not supported] The id xref is linking to, is missing in the de-tree, but present in the missing-ids.xml file: para id=ini.com.allow-dcom/para In the english file in question (faq/com.xml) xref is used like: xref linkend=ini.com.allow-dcom/ As this points to para id=ini.com.allow-dcom/para in missing-ids.xml for the de tree, obviously no link text can be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? Possibilities (other than updating the german manual ;-)): 1.) use xreflabel 2.) produce content for the para's in missing-ids.xml 3.) split the faq No splitting will help this error message popping up, since it occurs in different places in different translations. It can happen anytime you have an outdated file in your translation. Yeah, I know. It was the subtle attempt to suggest splitting of large files. (but that's another story) The problem is the increased usage of xref. Previously authors were encouraged to use link to add internal links, which requires text content, so this was no problem. The adoption of xref lead to this problem. Should we avoid using xref? 1. What would we put into para xreflabel=... in place of the dots in the missing-ids.xml file? The proper link-test? Sure, this depends on the content of the id=.. For the example para id=ini.com.allow-dcom this would become para id=ini.com.allow-dcom xreflabel=com.allow_dcom 2. How would this be better then the previous option? In no case, just another option to generate link text via xref. para id=ini.com.allow-dcomcom.allow_dcom/para Either way, if we choose option 1 or 2 it increases processing time, maybe we can place just some generic text inside? Not nice also... 3. This is not just a faq problem. I agree, it was just an example of one missing-id. Currently the missing-ids.xml file is a bit pointless; it only serves a technichal purpose: building the manual, and this not too clever as it produces unneccesary warnings and no content for the readers (I don't blame anyone for this!) Either we don't use xref or we should fix the generating of missing id's. In general, I really do not care much about this problem and if we can come up with a solution - fine, if not life goes on. However, the build process for translated manuals should not be hindered by this issue. Friedhelm p.s.: True, there are some big files in the FAQ folder.. See above, we might want to split them?
Re: [PHP-DOC] build failure [de]
Nuno Lopes wrote: Possibilities (other than updating the german manual ;-)): 1.) use xreflabel 2.) produce content for the para's in missing-ids.xml 3.) split the faq If 2) fixes the problem, I would go for it. This should fix the problem (not tested), I only did a quick test with xreflabel. Friedhelm
[PHP-DOC] cvs: phpdoc /en/appendices aliases.xml
betzSat Sep 10 11:06:17 2005 EDT Modified files: /phpdoc/en/appendices aliases.xml Log: odbc_* funcs belong to ODBC http://cvs.php.net/diff.php/phpdoc/en/appendices/aliases.xml?r1=1.30r2=1.31ty=u Index: phpdoc/en/appendices/aliases.xml diff -u phpdoc/en/appendices/aliases.xml:1.30 phpdoc/en/appendices/aliases.xml:1.31 --- phpdoc/en/appendices/aliases.xml:1.30 Wed Sep 1 17:36:12 2004 +++ phpdoc/en/appendices/aliases.xmlSat Sep 10 11:06:15 2005 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.30 $ -- +!-- $Revision: 1.31 $ -- appendix id=aliases titleList of Function Aliases/title para @@ -1083,12 +1083,12 @@ row entryodbc_do/entry entryfunctionodbc_exec/function/entry - entrylink linkend=ref.uodbcOCI8/link/entry + entrylink linkend=ref.uodbcODBC/link/entry /row row entryodbc_field_precision/entry entryfunctionodbc_field_len/function/entry - entrylink linkend=ref.uodbcOCI8/link/entry + entrylink linkend=ref.uodbcODBC/link/entry /row row entryoutput/entry
[PHP-DOC] #32943 [Bgs]: is_numeric validates 3e0
ID: 32943
Updated by: [EMAIL PROTECTED]
Reported By: pmorgan at ukds dot net
Status: Bogus
-Bug Type: Scripting Engine problem
+Bug Type: Documentation problem
Operating System: Linux
PHP Version: 4.3.10
New Comment:
reopen this as documentation bug.
number could also be given in e-notation, hex-notation,
octal-notation
Previous Comments:
[2005-05-04 14:40:54] pmorgan at ukds dot net
That needs to go into the manual number in e-notation, which I
understand, or even better as an additional flag allow_e-notation.
It's the last error I would have expected and is very misleading AFAIK.
[2005-05-04 14:40:45] pmorgan at ukds dot net
That needs to go into the manual number in e-notation, which I
understand, or even better as an additional flag allow_e-notation.
It's the last error I would have expected and is very misleading AFAIK.
[2005-05-04 14:30:10] [EMAIL PROTECTED]
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php
3e0 is a number in e-notation, which is of course a numerical string
[2005-05-04 12:29:00] pmorgan at ukds dot net
typo
[2005-05-04 12:28:04] pmorgan at ukds dot net
Description:
With some server side validation I inadvertenly entered 3e0 into the
textbox, it validated to my suprise. Would have expected this to throw
a false
Reproduce code:
---
echo is_numeric('3e00')? 'true': 'false';
Expected result:
false;
In fact anything without 0-9 and a . I would expect a false !
--
Edit this bug report at http://bugs.php.net/?id=32943edit=1
[PHP-DOC] #32943 [Bgs-Opn]: is_numeric validates 3e0
ID: 32943 Updated by: [EMAIL PROTECTED] Reported By: pmorgan at ukds dot net -Status: Bogus +Status: Open Bug Type: Documentation problem Operating System: Linux PHP Version: 4.3.10 New Comment: changed status Previous Comments: [2005-09-08 13:21:15] [EMAIL PROTECTED] reopen this as documentation bug. number could also be given in e-notation, hex-notation, octal-notation [2005-05-04 14:40:54] pmorgan at ukds dot net That needs to go into the manual number in e-notation, which I understand, or even better as an additional flag allow_e-notation. It's the last error I would have expected and is very misleading AFAIK. [2005-05-04 14:40:45] pmorgan at ukds dot net That needs to go into the manual number in e-notation, which I understand, or even better as an additional flag allow_e-notation. It's the last error I would have expected and is very misleading AFAIK. [2005-05-04 14:30:10] [EMAIL PROTECTED] Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php 3e0 is a number in e-notation, which is of course a numerical string [2005-05-04 12:29:00] pmorgan at ukds dot net typo The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/32943 -- Edit this bug report at http://bugs.php.net/?id=32943edit=1
[PHP-DOC] cvs: phpdoc /howto scripts.xml
betzThu Sep 8 10:09:04 2005 EDT Modified files: /phpdoc/howto scripts.xml Log: typos http://cvs.php.net/diff.php/phpdoc/howto/scripts.xml?r1=1.2r2=1.3ty=u Index: phpdoc/howto/scripts.xml diff -u phpdoc/howto/scripts.xml:1.2 phpdoc/howto/scripts.xml:1.3 --- phpdoc/howto/scripts.xml:1.2Wed Sep 7 17:25:36 2005 +++ phpdoc/howto/scripts.xmlThu Sep 8 10:09:02 2005 @@ -90,13 +90,13 @@ para The purpose of the extension, specified by an ID. There are several IDs available, which can be consulted in the - filenameen/entensions.ent/filename file. They look like + filenameen/extensions.ent/filename file. They look like literaldatabase.vendors/literal or literalxml/literal. /para para If none of the available categories fits your extension, you can create a new one. To do so, you must add a new entity in the - filenameen/entensions.ent/filename file, like: + filenameen/extensions.ent/filename file, like: literallt;!ENTITY extcat.purpose.xml 'lt;titlegt;XML Manipulationlt;/titlegt;'gt;/literal. After this, you still need to edit filenameen/appendices/extensions.xml/filename and
[PHP-DOC] cvs: phpdoc /en/reference/session_pgsql .cvsignore configure.xml ini.xml reference.xml /en/reference/session_pgsql/functions session-pgsql-status.xml
betzThu Sep 8 12:03:16 2005 EDT Added files: /phpdoc/en/reference/session_pgsql .cvsignore configure.xml ini.xml reference.xml /phpdoc/en/reference/session_pgsql/functions session-pgsql-status.xml Log: move session_pgsql from peardoc to phpdoc http://cvs.php.net/co.php/phpdoc/en/reference/session_pgsql/.cvsignore?r=1.1p=1 Index: phpdoc/en/reference/session_pgsql/.cvsignore +++ phpdoc/en/reference/session_pgsql/.cvsignore functions.xml http://cvs.php.net/co.php/phpdoc/en/reference/session_pgsql/configure.xml?r=1.1p=1 Index: phpdoc/en/reference/session_pgsql/configure.xml +++ phpdoc/en/reference/session_pgsql/configure.xml ?xml version=1.0 encoding=iso-8859-1? !-- $Revision: 1.1 $ -- section id=session-pgsql.installation reftitle.install; para Short installation note: itemizedlist listitem simpara Untar the literaltar.gz/literal archive into filename class=directoryphp4/ext/filename (Latest official releases can be found at SourceForge ulink url=url.phpform;PHP Form Extension Project/ulink) /simpara /listitem listitem simpara If the new directory is now called something like literalsession_pgsql/literal. You should name it to literalsession_pgsql/literal (except you only want to build it as self-contained php-module). /simpara /listitem listitem simparaRun userinput./buildconf/userinput in php4/simpara /listitem listitem simpara Run userinputconfigure/userinput option role=configure--with-session-pgsql/option (and your other options) /simpara /listitem listitem simparauserinputmake; make install/userinput/simpara /listitem /itemizedlist /para /section !-- 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 indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/session_pgsql/ini.xml?r=1.1p=1 Index: phpdoc/en/reference/session_pgsql/ini.xml +++ phpdoc/en/reference/session_pgsql/ini.xml ?xml version=1.0 encoding=iso-8859-1? !-- $Revision: 1.1 $ -- section id=session-pgsql.configuration reftitle.runtime; extension.runtime; para PostgreSQL session save handler is still under development. Refer to the filenameREADME/filename file in the source distribution for configuration details. /para /section !-- 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 indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/session_pgsql/reference.xml?r=1.1p=1 Index: phpdoc/en/reference/session_pgsql/reference.xml +++ phpdoc/en/reference/session_pgsql/reference.xml ?xml version=1.0 encoding=iso-8859-1? !-- $Revision: 1.1 $ -- !-- Purpose: basic.session -- !-- Membership: pecl, external -- !-- State: experimental-- !-- Author: Yasuo Ohgaki [EMAIL PROTECTED] -- reference id=ref.session-pgsql titlePostgreSQL Session Save Handler/title titleabbrevSession PgSQL/titleabbrev partintro section id=session-pgsql.intro reftitle.intro; warn.experimental; note.no-windows.extension; para This module provide additional session save handler for session module using PostgreSQL as a storage. literaluser/literal session save handler may be used, but this module is written in C. Therefore, this module is roughly 2 times faster than save handler written in PHP script. /para para Fail-over and load balance is planned to be implemented, but they are not available now. /para note simpara There will be functions for this module, but it is not available now. /simpara /note /section section id=session-pgsql.requirements reftitle.required; para You need at least PHP 4.1, PostgreSQL 7.1 and MM 1.1.3 /para /section reference.session-pgsql.configure; reference.session-pgsql.ini; section id=session-pgsql.contact titleContact Information/title para I have at the moment not very much time to further develop this extension. I will implement more and more features in the near future. /para para If you have comments, bug fixes, enhancements or want to help developing
Re: [PHP-DOC] cvs: phpdoc /scripts xml_proto.php
Jakub Vrana wrote: fwrite($fp, '?xml version=1.0 encoding=iso-8859-1?'.\n . - '!-- $Revision: 1.34 $ --'.\n . + '!-- $Revision: 1.35 $ --'.\n . + !-- Purpose: --\n . + !-- Membership: --\n . !-- Generated by xml_proto.php v . $version . . Found in /scripts directory of phpdoc. --\n . reference id=\ref. . $extension_name . \\n . title$extension_name Functions/title\n . @@ -244,7 +246,7 @@ $functype = trim($funclist[$i][function_type]); fwrite($fp, '?xml version=1.0 encoding=iso-8859-1?'.\n . - '!-- $Revision: 1.34 $ --'.\n . + '!-- $Revision: 1.35 $ --'.\n . !-- Generated by xml_proto.php v . $version . . Found in /scripts directory of phpdoc. --\n . refentry id=\function. . $fixname . \\n . refnamediv\n . I guess those revision comments should be the revision number of the generated file not the revision number from xml_proto.php itself. So this should be '!-- $Revision: 1.1 $ --'.\n . instead '!-- $Revision: 1.35 $ --'.\n . Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/session_pgsql/functions session-pgsql-status.xml
betzThu Sep 8 14:24:45 2005 EDT Modified files: /phpdoc/en/reference/session_pgsql/functions session-pgsql-status.xml Log: correct return type http://cvs.php.net/diff.php/phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml?r1=1.1r2=1.2ty=u Index: phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml diff -u phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml:1.1 phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml:1.2 --- phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml:1.1 Thu Sep 8 12:03:16 2005 +++ phpdoc/en/reference/session_pgsql/functions/session-pgsql-status.xml Thu Sep 8 14:24:45 2005 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.1 $ -- +!-- $Revision: 1.2 $ -- !-- splitted from ./en/functions/session-pgsql.xml, last change in rev 1.2 -- refentry id=function.session-pgsql-status refnamediv @@ -11,7 +11,7 @@ reftitle.description; methodsynopsis typearray/typemethodnamesession_pgsql_status/methodname - methodparamparametervoid/parameter/methodparam + void/ /methodsynopsis warn.experimental.func; warn.undocumented.func;
[PHP-DOC] cvs: phpdoc /en/reference/session_pgsql/functions session-pgsql-add-error.xml session-pgsql-get-error.xml session-pgsql-get-field.xml session-pgsql-reset.xml session-pgsql-set-field.xml
betzThu Sep 8 14:25:44 2005 EDT
Added files:
/phpdoc/en/reference/session_pgsql/functions
session-pgsql-add-error.xml
session-pgsql-get-error.xml
session-pgsql-get-field.xml
session-pgsql-reset.xml
session-pgsql-set-field.xml
Log:
more function skeletons for session_pgsql
http://cvs.php.net/co.php/phpdoc/en/reference/session_pgsql/functions/session-pgsql-add-error.xml?r=1.1p=1
Index: phpdoc/en/reference/session_pgsql/functions/session-pgsql-add-error.xml
+++ phpdoc/en/reference/session_pgsql/functions/session-pgsql-add-error.xml
?xml version=1.0 encoding=iso-8859-1?
!-- $Revision: 1.1 $ --
!-- Generated by xml_proto.php v2.2. Found in /scripts directory of phpdoc. --
refentry id=function.session-pgsql-add-error
refnamediv
refnamesession_pgsql_add_error/refname
refpurposeIncrements error counts and sets last error message/refpurpose
/refnamediv
refsect1 role=description
reftitle.description;
methodsynopsis
typebool/typemethodnamesession_pgsql_add_error/methodname
methodparamtypeint/typeparametererror_level/parameter/methodparam
methodparam
choice=opttypestring/typeparametererror_message/parameter/methodparam
/methodsynopsis
warn.undocumented.func;
/refsect1
refsect1 role=parameters
reftitle.parameters;
para
variablelist
varlistentry
termparametererror_level/parameter/term
listitem
para
/para
/listitem
/varlistentry
varlistentry
termparametererror_message/parameter/term
listitem
para
/para
/listitem
/varlistentry
/variablelist
/para
/refsect1
refsect1 role=returnvalues
reftitle.returnvalues;
para
return.success;
/para
/refsect1
refsect1 role=seealso
reftitle.seealso;
para
simplelist
memberfunctionsession_pgsql_get_error/function/member
/simplelist
/para
/refsect1
/refentry
!-- 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
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:../../../../manual.ced
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
--
http://cvs.php.net/co.php/phpdoc/en/reference/session_pgsql/functions/session-pgsql-get-error.xml?r=1.1p=1
Index: phpdoc/en/reference/session_pgsql/functions/session-pgsql-get-error.xml
+++ phpdoc/en/reference/session_pgsql/functions/session-pgsql-get-error.xml
?xml version=1.0 encoding=iso-8859-1?
!-- $Revision: 1.1 $ --
!-- Generated by xml_proto.php v2.2. Found in /scripts directory of phpdoc. --
refentry id=function.session-pgsql-get-error
refnamediv
refnamesession_pgsql_get_error/refname
refpurposeReturns number of errors and last error message/refpurpose
/refnamediv
refsect1 role=description
reftitle.description;
methodsynopsis
typearray/typemethodnamesession_pgsql_get_error/methodname
methodparam
choice=opttypebool/typeparameterwith_error_message/parameter/methodparam
/methodsynopsis
para
Get the number of errors and optional the errror messages.
/para
/refsect1
refsect1 role=parameters
reftitle.parameters;
para
variablelist
varlistentry
termparameterwith_error_message/parameter/term
listitem
para
Set to true; the literal error message for each error is also returned.
/para
/listitem
/varlistentry
/variablelist
/para
/refsect1
refsect1 role=returnvalues
reftitle.returnvalues;
para
The number of errors are returned as typearray/type.
/para
/refsect1
!-- Use when examples exist
refsect1 role=examples
reftitle.examples;
para
example
titleA functionsession_pgsql_get_error/function example/title
para
Any text that describes the purpose of the example, or
what goes on in the example should go here (inside the
example tag, not out
/para
programlisting role=php
![CDATA[
?php
if ($anexample === true) {
echo 'Use the PEAR Coding Standards';
}
?
]]
/programlisting
example.outputs;
screen
![CDATA[
Use the PEAR Coding Standards
]]
/screen
/example
/para
/refsect1
--
refsect1 role=seealso
reftitle.seealso;
para
simplelist
memberfunctionsession_pgsql_add_error/function/member
/simplelist
/para
/refsect1
/refentry
!-- 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
indent-tabs-mode:nil
[PHP-DOC] cvs: phpdoc /scripts xml_proto.php
betzThu Sep 8 15:29:20 2005 EDT
Modified files:
/phpdoc/scripts xml_proto.php
Log:
no tabs
http://cvs.php.net/diff.php/phpdoc/scripts/xml_proto.php?r1=1.35r2=1.36ty=u
Index: phpdoc/scripts/xml_proto.php
diff -u phpdoc/scripts/xml_proto.php:1.35 phpdoc/scripts/xml_proto.php:1.36
--- phpdoc/scripts/xml_proto.php:1.35 Wed Sep 7 04:20:42 2005
+++ phpdoc/scripts/xml_proto.phpThu Sep 8 15:29:19 2005
@@ -16,7 +16,7 @@
| Authors: Brad House [EMAIL PROTECTED] |
+--+
- $Id: xml_proto.php,v 1.35 2005/09/07 08:20:42 vrana Exp $
+ $Id: xml_proto.php,v 1.36 2005/09/08 19:29:19 betz Exp $
*/
/*
@@ -49,8 +49,8 @@
- Generation of references.xml template
- functions with optional arguments would not parse properly,
now it does
- Wildcard scanning is now allowed
-- Requires PHP 4.3.0-pre1 or higher now
-- Usage is totally different
+ - Requires PHP 4.3.0-pre1 or higher now
+ - Usage is totally different
05/06/04 v2.1 - Corrected filenames for OO functions
01/03/05 v2.2 - Implemented the new doc style
08/08/05 v2.3 - Refpurpose is on one line
@@ -159,7 +159,7 @@
}
fwrite($fp, '?xml version=1.0 encoding=iso-8859-1?'.\n .
- '!-- $Revision: 1.35 $ --'.\n .
+ '!-- $Revision: 1.36 $ --'.\n .
!-- Purpose: --\n .
!-- Membership: --\n .
!-- Generated by xml_proto.php v . $version . . Found in /scripts
directory of phpdoc. --\n .
@@ -246,7 +246,7 @@
$functype = trim($funclist[$i][function_type]);
fwrite($fp, '?xml version=1.0 encoding=iso-8859-1?'.\n .
- '!-- $Revision: 1.35 $ --'.\n .
+ '!-- $Revision: 1.36 $ --'.\n .
!-- Generated by xml_proto.php v . $version . . Found in
/scripts directory of phpdoc. --\n .
refentry id=\function. . $fixname . \\n .
refnamediv\n .
@@ -443,19 +443,19 @@
case '\n':
case ' ':
if (!$spaces) {
- $spaces=1;
+ $spaces=1;
$temp .= ' ';
- $temp_len++;
+ $temp_len++;
}
- break;
+break;
default:
if ($c != '\r' $c != '\n') {
$spaces=0;
- $temp .= $c;
- $temp_len++;
+ $temp .= $c;
+ $temp_len++;
}
- break;
+break;
}
}
function_add_purpose($func_num, $temp);
@@ -464,129 +464,129 @@
function parse_proto($proto)
{
- $len=0;
- $i=0;
- $c=0;
- $done=0;
- $start=0;
- $func_number=-1;
- $got_proto_def=0;
- $got_proto_type=0;
- $got_proto_name=0;
- $got_arg_type=0;
- $start_args=0;
- $temp=;
- $temp2=;
- $temp_len=0;
- $isopt=0;
-
- $len=strlen($proto);
-
- for ($i=0; $i$len; $i++) {
-$c=substr($proto, $i, 1);
-switch ($c) {
- case '\r':
- case '\n':
- case ' ':
-if ($temp_len) {
- if (!$got_proto_def) {
- if (strcasecmp($temp, proto) != 0) {
- // Possibly just a comment, don't output error info
- // echo Not a proper proto definition: $proto\n;
- return(0);
- } else {
- $got_proto_def=1;
- }
- } else if (!$got_proto_type) {
- $func_number=new_function();
-function_add_type($func_number, $temp);
- $got_proto_type=1;
- } else if (!$got_proto_name) {
-function_add_name($func_number, $temp);
- $got_proto_name=1;
- } else if ($start_args !$got_arg_type) {
-$got_arg_type=1;
- $temp2=$temp;
- } else if ($start_args $got_arg_type) {
- $got_arg_type=0;
-function_add_arg($func_number, $temp2, $temp, $isopt);
- $temp2=;
- }
- $temp_len=0;
- $temp=;
-}
- break;
+$len=0;
+$i=0;
+$c=0;
+$done=0;
+$start=0;
+$func_number=-1;
+$got_proto_def=0;
+$got_proto_type=0;
+$got_proto_name=0;
+$got_arg_type=0;
+$start_args=0;
+$temp=;
+$temp2=;
+$temp_len=0;
+$isopt=0;
+
+$len=strlen($proto);
+
+for ($i=0; $i$len; $i++) {
+$c=substr($proto, $i, 1);
+switch ($c) {
+case '\r':
+case '\n':
+case ' ':
+if ($temp_len) {
+ if (!$got_proto_def) {
+if (strcasecmp($temp, proto) != 0) {
+ // Possibly just a comment, don't output error info
+ // echo Not a proper proto definition: $proto\n;
+ return(0);
+} else {
+$got_proto_def=1;
+}
+ } else if (!$got_proto_type) {
+ $func_number=new_function();
+ function_add_type($func_number
