[PHP-DOC] #19575 [Dup-Asn]: Boolean prints 1 for TRUE but nothing for FALSE
ID: 19575 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Duplicate +Status: Assigned Bug Type: Documentation problem Operating System: Red Hat Linux 7.2 PHP Version: 4.2.3 -Assigned To: +Assigned To: goba New Comment: I'll correct this sometime later if noone picks it up. I have no time now, sorry. Previous Comments: [2002-10-06 21:25:28] [EMAIL PROTECTED] Goba: I understand the need for such a feature I just don't like the implementation. But hey, I don't like loosely typed languaged in the first place ;) But ... all I'm asking for is better documentation. I didn't expect this behaviour and couldn't find any documentation to help figureout why what I was not expecting was happening. [2002-10-05 10:04:48] [EMAIL PROTECTED] This feature(!) is there so you can convert from booleans to strings, then back to booleans or to integers and then to booleans, and you get the same boolean you started from... boolean - string - boolean TRUE1 TRUE FALSE FALSE boolean - string - integer - boolean TRUE11 TRUE FALSE0 FALSE In php code: $false_bool = (boolean) (int) (string) FALSE; Goba [2002-10-05 09:58:17] [EMAIL PROTECTED] Dupe of bug #18411 [2002-09-24 06:56:43] [EMAIL PROTECTED] A boolean of TRUE will print as 1 whereas FALSE prints as This has caused me a problem since I had assume that TRUE would print as TRUE and FALSE would print as FALSE. Could you add this to the documentation. I could understand 1/0, TRUE/FALSE, but 1/ is not evident at first. I'd even suggest a change request that booleans print out as TRUE/FALSE (since booleans really should not be 1/0 integers or empty/non-empty strings but BOOLEANS) but I'm sure that would ge shot down. :) -- Edit this bug report at http://bugs.php.net/?id=19575edit=1 -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Revision Check
What is the problem in that file??? Credits are counted for Renato. Goba [one [EMAIL PROTECTED]] - Original Message - From: André LFS Bacci To: [EMAIL PROTECTED] Sent: Monday, October 07, 2002 6:19 AM Subject: [PHP-DOC] Revision Check The revcheck system is not workink proprerly in revision-tags with CREDITS:. See in the source of http://www.php.net/manual/pt_BR/revcheck.html.gz for --!-- []s André Æ
[PHP-DOC] cvs: phpdoc /en/reference/session reference.xml
samesch Mon Oct 7 06:47:16 2002 EDT Modified files: /phpdoc/en/reference/sessionreference.xml Log: made 'global' a link Index: phpdoc/en/reference/session/reference.xml diff -u phpdoc/en/reference/session/reference.xml:1.16 phpdoc/en/reference/session/reference.xml:1.17 --- phpdoc/en/reference/session/reference.xml:1.16 Thu Oct 3 23:05:09 2002 +++ phpdoc/en/reference/session/reference.xml Mon Oct 7 06:47:15 2002 -1,5 +1,5 ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.16 $ -- +!-- $Revision: 1.17 $ -- reference id=ref.session titleSession handling functions/title titleabbrevSessions/titleabbrev -114,10 +114,12 varname$_GET/varname, varname$_REQUEST/varname and so on. Unlike varname$HTTP_SESSION_VARS/varname, varname$_SESSION/varname is always global. Therefore, you do not - need to use literalglobal/literal for - varname$_SESSION/varname. Please note that this documentation - has been changed to use varname$_SESSION/varname everywhere. You can - substitute varname$HTTP_SESSION_VARS/varname for + need to use the link + linkend=language.variables.scopecommandglobal/command/link + keyword for varname$_SESSION/varname. Please note that this + documentation has been changed to use + varname$_SESSION/varname everywhere. You can substitute + varname$HTTP_SESSION_VARS/varname for varname$_SESSION/varname, if you prefer the former. /para para -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/reference/session reference.xml
samesch Mon Oct 7 07:12:19 2002 EDT Modified files: /phpdoc/en/reference/sessionreference.xml Log: no use of brackets with function tags; added function tags Index: phpdoc/en/reference/session/reference.xml diff -u phpdoc/en/reference/session/reference.xml:1.17 phpdoc/en/reference/session/reference.xml:1.18 --- phpdoc/en/reference/session/reference.xml:1.17 Mon Oct 7 06:47:15 2002 +++ phpdoc/en/reference/session/reference.xml Mon Oct 7 07:12:19 2002 -1,5 +1,5 ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.17 $ -- +!-- $Revision: 1.18 $ -- reference id=ref.session titleSession handling functions/title titleabbrevSessions/titleabbrev -145,9 +145,9 varname$HTTP_SESSION_VARS/varname with PHP 4.0.6 or less) is recommended for improved security and code readablity. With varname$_SESSION/varname, there is no need to use the - functionsession_register()/function, - functionsession_unregister()/function, - functionsession_is_registered()/function functions. Session variables + functionsession_register/function, + functionsession_unregister/function, + functionsession_is_registered/function functions. Session variables are accessible like any other variables. example title -204,8 +204,9 variable. Upon a restart of a session, these variables will be restored to corresponding global variables. Since PHP must know which global variables are registered as session variables, users need to register - variables with session_register() function. You can avoid this by simply - setting entries in varname$_SESSION/varname. + variables with functionsession_register/function function. + You can avoid this by simply setting entries in + varname$_SESSION/varname. caution para If you are using -258,12 +259,13 /para para Additionally, if you register a new session variable by using - functionsession_register()/function, the entry in the global scope + functionsession_register/function, the entry in the global scope and the varname$_SESSION/varname entry will not reference the same - value until the next session start (this applies to PHP 4.2 and before - only). I.e. a modification to the global variable will not be reflected - by the varname$_SESSION/varname entry. This is unlikely to matter in - practice and has been corrected in PHP 4.3. + value until the next functionsession_start/function (this + applies to PHP 4.2 and before only). I.e. a modification to the + global variable will not be reflected by the + varname$_SESSION/varname entry. This is unlikely to matter + in practice and has been corrected in PHP 4.3. /para /section -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] #19802 [Opn]: wrong docs curl requirment
ID: 19802 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Documentation problem Operating System: RH linux 7.1 PHP Version: 4.2.3 New Comment: This actually depends on the PHP version you install. Previous Comments: [2002-10-07 09:58:11] [EMAIL PROTECTED] on http://www.php.net/manual/en/ref.curl.php mentions: PHP will not work with any version of CURL below version 7.0.2-beta but on configure i get: configure: error: cURL version 7.9 or later is required to compile php with cURL support when i have 7.4.x -- Edit this bug report at http://bugs.php.net/?id=19802edit=1 -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] #19803 [NEW]: php.net/mcrypt documentation should include addition information
From: [EMAIL PROTECTED] Operating system: AIX 4.3.3 PHP version: 4.2.3 PHP Bug Type: Documentation problem Bug description: php.net/mcrypt documentation should include addition information I had been stuck with hte problem for almost a week, it wasn't until someone's posting in the php newgroup that saved my hide from further struggle. What happen is that I followed the documentation at php.net/mcrypt and I had problem with algorithm. I checked the PHP Info (by using phpinfo() function) and it said that mcrypt is supported but no ciphers. The documenation should mentioned that mcrypt software is needed along with libmcrypt software, so I would have the cipher be supported. I'm new to libmcrypt and I got the impression that it have everything in it. I'm not familiar with mcrypt as well. Now that my understand had been enhanced, I figured the document will need to be updated or to include some information so in the future, it would benefit everyone better, including people who may be confused with libmcrypt and mcrypt. -- Edit bug report at http://bugs.php.net/?id=19803edit=1 -- Try a CVS snapshot: http://bugs.php.net/fix.php?id=19803r=trysnapshot Fixed in CVS: http://bugs.php.net/fix.php?id=19803r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=19803r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=19803r=needtrace Try newer version: http://bugs.php.net/fix.php?id=19803r=oldversion Not developer issue:http://bugs.php.net/fix.php?id=19803r=support Expected behavior: http://bugs.php.net/fix.php?id=19803r=notwrong Not enough info:http://bugs.php.net/fix.php?id=19803r=notenoughinfo Submitted twice:http://bugs.php.net/fix.php?id=19803r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=19803r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=19803r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=19803r=dst IIS Stability: http://bugs.php.net/fix.php?id=19803r=isapi -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] #19802 [Com]: wrong docs curl requirment
ID: 19802 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Documentation problem Operating System: RH linux 7.1 PHP Version: 4.2.3 New Comment: but it's written there that the php 4 = 4.2 when i have 4.X Previous Comments: [2002-10-07 10:03:19] [EMAIL PROTECTED] This actually depends on the PHP version you install. [2002-10-07 09:58:11] [EMAIL PROTECTED] on http://www.php.net/manual/en/ref.curl.php mentions: PHP will not work with any version of CURL below version 7.0.2-beta but on configure i get: configure: error: cURL version 7.9 or later is required to compile php with cURL support when i have 7.4.x -- Edit this bug report at http://bugs.php.net/?id=19802edit=1 -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions is-executable.xml
mfischerMon Oct 7 11:45:38 2002 EDT Modified files: /phpdoc/en/reference/filesystem/functions is-executable.xml Log: - Document latest scientific researches on PHP functions (thanks to Marc Boeren for finding this). Index: phpdoc/en/reference/filesystem/functions/is-executable.xml diff -u phpdoc/en/reference/filesystem/functions/is-executable.xml:1.2 phpdoc/en/reference/filesystem/functions/is-executable.xml:1.3 --- phpdoc/en/reference/filesystem/functions/is-executable.xml:1.2 Wed Apr 17 02:38:08 2002 +++ phpdoc/en/reference/filesystem/functions/is-executable.xml Mon Oct 7 11:45:38 +2002 -1,5 +1,5 ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- !-- splitted from ./en/functions/filesystem.xml, last change in rev 1.2 -- refentry id=function.is-executable refnamediv -24,6 +24,12 linkend=features.remote-filesremote files/link; the file to be examined must be accessible via the server's filesystem. /simpara +note + simpara + This function is emphasis role=strongnot/emphasis available on + Win32. + /simpara +/note para See also functionis_file/function and functionis_link/function. -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] #19802 [Opn-Csd]: wrong docs curl requirment
ID: 19802 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: RH linux 7.1 PHP Version: 4.2.3 New Comment: Just follow ./configure and install the latest cURL. I'll update the manual that the current required version is 7.9. Derick Previous Comments: [2002-10-07 10:21:34] [EMAIL PROTECTED] but it's written there that the php 4 = 4.2 when i have 4.X [2002-10-07 10:03:19] [EMAIL PROTECTED] This actually depends on the PHP version you install. [2002-10-07 09:58:11] [EMAIL PROTECTED] on http://www.php.net/manual/en/ref.curl.php mentions: PHP will not work with any version of CURL below version 7.0.2-beta but on configure i get: configure: error: cURL version 7.9 or later is required to compile php with cURL support when i have 7.4.x -- Edit this bug report at http://bugs.php.net/?id=19802edit=1 -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/reference/curl reference.xml
derick Mon Oct 7 13:03:21 2002 EDT Modified files: /phpdoc/en/reference/curl reference.xml Log: - Fix curl requirements Index: phpdoc/en/reference/curl/reference.xml diff -u phpdoc/en/reference/curl/reference.xml:1.3 phpdoc/en/reference/curl/reference.xml:1.4 --- phpdoc/en/reference/curl/reference.xml:1.3 Fri Apr 19 11:06:04 2002 +++ phpdoc/en/reference/curl/reference.xml Mon Oct 7 13:03:21 2002 -1,5 +1,5 ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.3 $ -- +!-- $Revision: 1.4 $ -- reference id=ref.curl titleCURL, Client URL Library Functions/title titleabbrevCURL/titleabbrev -28,7 +28,8 In order to use the CURL functions you need to install the ulink url=url.curl;CURL/ulink package. PHP requires that you use CURL 7.0.2-beta or higher. PHP will not work with any version of - CURL below version 7.0.2-beta. + CURL below version 7.0.2-beta. From PHP version 4.2.3 you will atleast + need CURL version 7.9.0 or higher. /para /section -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] #19767 [Ana-Csd]: dl isn´t supported on multi-threading servers
ID: 19767 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Analyzed +Status: Closed Bug Type: Documentation problem Operating System: not apply PHP Version: 4.2.3 New Comment: This bug has been fixed in CVS. In case this was a PHP problem, snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites in short time. Thank you for the report, and for helping us make PHP better. Previous Comments: [2002-10-06 12:49:20] [EMAIL PROTECTED] feel free to join the documentation translation team. [2002-10-06 12:01:25] [EMAIL PROTECTED] please compare http://www.php.net/manual/en/function.dl.php http://www.php.net/manual/de/function.dl.php okay, but my bug report is your fault. e05 [2002-10-05 15:27:36] [EMAIL PROTECTED] http://www.php.net/manual/en/function.dl.php see the second note: Note: dl() is not supported in multithreaded Web servers. Use the extensions statement in your php.ini when operating under such an environment. However, the CGI and CLI build are not affected ! [2002-10-05 14:49:42] [EMAIL PROTECTED] yes it is no doc problem. But theres is no note for that in the manual. e05 [2002-10-05 08:08:31] [EMAIL PROTECTED] 1.) not a doc problem 2.) duplicate 3.) submitted twice 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/19767 -- Edit this bug report at http://bugs.php.net/?id=19767edit=1 -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] Changes in Revcheck
Hi all, I'd like to change some things in the revcheck-system, but want to agree upon it first. The changes I mean are: 1.) Change the filesize-criteria for critical files from 10kB to 2kB Since the bananasplit, the filesizes devreased dramatically, and the chance, that a 2kB file increases to 10 kB is not very realistic. 2.) Change the age-criteria for critical files to the last change-date of the en-file Currently, if you've synced a file 30 days ago, and today the corresp. en-file gets changed, the status becomes immediately critical. If we change this to the last change of en-files, we lose the status critical with each change (up to 9 times), but I think it's the better choice (if I havent overseen something :) 3.) Add at least the diff of the file-sizes in the table Files without Revision-comment That might be only a prob. for the german lang, but maybe also for the other traditional langs: We have 744 such files, of which the most are orphaned (and the translators most not active anymore) IMO. With this info we could easily see the biggest differences and act accordingly without a bad conscience for stealing files, and prevent so bugs like #19767 (de:1,22kB, en:4,52kB). 4.) To discuss: Since the banasplit, the file-sizes are very small, and changes don't really take an eternity anymore. So my question: Does anybody still need the status in the output of the list of files (ready, working, etc.)? That's all for now, Thomas -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] HTML Help security patch
Someone have reported a problem with the .chm version of the german PHP-FAQ (http://www.dclp-faq.de) after installing an unchecked buffer fix (http://www.microsoft.com/technet/security/bulletin/ms02-055.asp) for Microsoft HTML Help. Are there any problems known with the PHP manual? Regards, Kai -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Changes in Revcheck
1.) Change the filesize-criteria for critical files from 10kB to 2kB Since the bananasplit, the filesizes devreased dramatically, and the chance, that a 2kB file increases to 10 kB is not very realistic. OK. 2.) Change the age-criteria for critical files to the last change-date of the en-file Currently, if you've synced a file 30 days ago, and today the corresp. en-file gets changed, the status becomes immediately critical. If we change this to the last change of en-files, we lose the status critical with each change (up to 9 times), but I think it's the better choice (if I havent overseen something :) I cannot fully understand what you propose here... 3.) Add at least the diff of the file-sizes in the table Files without Revision-comment That might be only a prob. for the german lang, but maybe also for the other traditional langs: We have 744 such files, of which the most are orphaned (and the translators most not active anymore) IMO. With this info we could easily see the biggest differences and act accordingly without a bad conscience for stealing files, and prevent so bugs like #19767 (de:1,22kB, en:4,52kB). Add it if you feel it's needed. 4.) To discuss: Since the banasplit, the file-sizes are very small, and changes don't really take an eternity anymore. So my question: Does anybody still need the status in the output of the list of files (ready, working, etc.)? There are still many big files, which may need status information, so IMHO it would be nice to leave this in. Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
