[PHP-DOC] Bug #11714: Problem downloading docu
From: [EMAIL PROTECTED] Operating system: Linux PHP version: 4.0.6 PHP Bug Type: Documentation problem Bug description: Problem downloading docu Hi there Just wanted to bring it to your attn that the documentation page on www.php.net doesn't seem to work correctly. I cannot download (for English at least) the tarballs or zip files for plain/html docs. Cheers! Steve -- Edit Bug report at: http://bugs.php.net/?id=11714&edit=1
Re: [PHP-DOC] Convention: true/false
le 26/06/01 16:16, [EMAIL PROTECTED] à [EMAIL PROTECTED] a écrit : >> So, I'm still in favor of . Thats 1 contra, 1 pro. > > I'm against, so that makes 2 contra, 1 pro I'm against it too. Most of docs already use and I think Goba's right with TRUE not being a constant anymore. I would like to point out that spotting all True/FALse occurrences and turning them into tagged version would bring consistancy to docs, which is far beyond turning all literal -> constant. My two eurocents, for what's worth of it. Damien Seguy
Re: [PHP-DOC] experimental manual source for advanced translation handling
I simply totally agree. And as far as I'm concerned, you may turn on the evil mode :), i think it makes the whole process easier... (for example, we didnt' hear from 'Costin Cosoiu' anymore... Not impossible he thought it was to complicated, as is not unreasonable. For the master, large files are better (IMO), but indeed, for translations they aren't. But let's first hear some other opinions. Jeroen On Tue, 26 Jun 2001, Hartmut Holzgraefe wrote alot.
[PHP-DOC] cvs: phpdoc /en/functions math.xml
danbeck Tue Jun 26 22:46:01 2001 EDT Modified files: /phpdoc/en/functionsmath.xml Log: adding example to pi(), mostly so that they precision is obvious Index: phpdoc/en/functions/math.xml diff -u phpdoc/en/functions/math.xml:1.32 phpdoc/en/functions/math.xml:1.33 --- phpdoc/en/functions/math.xml:1.32 Tue Jun 26 22:42:17 2001 +++ phpdoc/en/functions/math.xmlTue Jun 26 22:46:01 2001 @@ -943,6 +943,16 @@ Returns an approximation of pi. + + + + +echo pi(); +// echo's 3.1415926535898 + + + +
[PHP-DOC] cvs: phpdoc /en/functions math.xml
danbeck Tue Jun 26 22:42:17 2001 EDT
Modified files:
/phpdoc/en/functionsmath.xml
Log:
number_format:
- added optional tags to optional parameters
- tweaked and added more examples
- moved example description under example block
- added "See also:" section
- removed several manual annotations that were
no longer needed because of these changes
Index: phpdoc/en/functions/math.xml
diff -u phpdoc/en/functions/math.xml:1.31 phpdoc/en/functions/math.xml:1.32
--- phpdoc/en/functions/math.xml:1.31 Sat Jun 23 22:10:51 2001
+++ phpdoc/en/functions/math.xmlTue Jun 26 22:42:17 2001
@@ -832,9 +832,9 @@
string number_format
float number
- int decimals
- string dec_point
- string thousands_sep
+ int decimals
+ string
+dec_point
+ string
+thousands_sep
@@ -860,23 +860,44 @@
a comma (",") between every group of thousands.
- For instance, French notation usually use two decimals,
- comma (',') as decimal separator, and space (' ') as
- thousand separator. This is achieved with this line :
-
+
+ number_format Example
+
+ For instance, French notation usually use two decimals,
+ comma (',') as decimal separator, and space (' ') as
+ thousand separator. This is achieved with this line :
+
-
+
+
+
+ See also: sprintf,
+ printf, sscanf and
+ fprintf.
+
+
[PHP-DOC] Bug #11702: IRC functions are not listed in the top level Table of Contents
From: [EMAIL PROTECTED] Operating system: PHP version: 4.0.6 PHP Bug Type: Documentation problem Bug description: IRC functions are not listed in the top level Table of Contents IRC functions are not listed in the top level documentation table of contents http://www.php.net/manual/en/ They are listed if you go to the 'Function Reference' Table of contents http://www.php.net/manual/en/funcref.php -- Edit Bug report at: http://bugs.php.net/?id=11702&edit=1
[PHP-DOC] Including PHP FAQ in documentation
Hi all, Here is a question : PHP FAQ (the one one the site), is now translated into French by university student. I'm working with them so as to xml-format this, and put it on the PHP CVS. - I remember talking with Goba (hi) about merging FAQ in php doc. Are there any opinion about this? I do think this will be an interesting place to gather doc, as FAQ represents common question. This way, they will be easily downloaded, and PHPmaster won't have to connect to use it. - Besides, this FAQ is translated, and PHP.net doesn't handle translation. If this is ok, I suggest making a faq directory, and break FAQ in several smaller files, so as to ease updates. Any opinion about this? (Egon, Jim, Goba or anyone else). Damien Seguy
Re: [PHP-DOC] experimental manual source for advanced translation handling
Jeroen van Wolffelaar wrote: > That the xml processing is slowed down is a pity, but it is > IMO not important. It's the output and the ease of modifying > /translating that counts, not the number of cycles wasted on it. the actual slowdown running jade was about 15sec with a total of 13min on my (slow disk) laptop, so nobody will really notice this > > [...] have them split up and recombined in the background > > during the actual built, but that is a different story ... > > The latter option is IMO best: you do not break CVS, you do > not have to change all files, and you can still edit the files > in a module-basis, rather than a single file for every minor > function. > For translation it is less useful, you'll need to get single functions > from the english sources when you want to translate a new function, > rather than simply copying a file. i still want to have each translation as a cvs module of its own, so breaking them up into single files might be a good chance to move them instead of updation the current repository maybe we could stay with the english version as is, but have a split up tree generated with the cvs version of the master file insterted as a comment at the very top so translaters could take this over as they do their work ... (although this would break the simple/stupid rule) and, hey, we could even build a web frontend for translators based on this, offering them only those parts for a change that really need one we could go even further and reduce translation files to the parts between ... and ... while getting und from the original file ;) -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
Re: [PHP-DOC] experimental manual source for advanced translation handling
> > i've done some experiments on one of the topics > > we had discussed here before the list went down > > > > all the files in the function directory have been split up > > in a general part and a subdirectory containing the actual > > refentries, one function refentry per file > > This sounds like a good idea to me, as you already argue. Me too :) Goba ... . . . . . Editor of the Hungarian PHP manual, Admin of the Hungarian PHP mirror
Re: [PHP-DOC] cvs: phpdoc / version.dsl version.xml
On Tue, 26 Jun 2001, Jeroen van Wolffelaar wrote: > >- ((equal-ci? (data nl) "abs") (literal "PHP 3, PHP 4 ")) > >+ ((equal-ci? (data nl) "abs") (literal "PHP 3, PHP 4 >= 4.0b1")) > > > Is it really necessary to specify that this function worked as of the first > beta? IMO it would be better if you stick with public releases, i.e. 4.0.0, > etc, and no beta's or RC's. Those versions are only really used during > development. The 4.0b series where publically released versions, so yes, it is neccesairy to discriminate between those. Derick
Re: [PHP-DOC] Convention: true/false
On Tue, 26 Jun 2001, Jeroen van Wolffelaar wrote: > So, I'm still in favor of . Thats 1 contra, 1 pro. I'm against, so that makes 2 contra, 1 pro Derick - PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED] SRM: Site Resource Manager - www.vl-srm.net -
Re: [PHP-DOC] Convention: true/false
I personally don't care for one over the other. I would only prefer that we are consistant and that it's rendered properly in the various manual formats. Daniel - Original Message - From: "Jeroen van Wolffelaar" <[EMAIL PROTECTED]> To: "Hojtsy Gabor" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; "PHP-DOC lista" <[EMAIL PROTECTED]> Sent: Tuesday, June 26, 2001 4:26 AM Subject: Re: [PHP-DOC] Convention: true/false > > TRUE *is not* a constant. There is a boolean type in PHP 4. > > TRUE *was* a constant in PHP 3... > > It is still defined as constant, just like NULL. > (zend_constants.c:117 : true/false constants) > THough you can argue > that it's better to see it as being a special keyword. > > It is a constant in the sense that its value never changes. > And, though layout shouldn't be an issue when it comes to xml, I like > the makeup op better in case of values like true... > > So, I'm still in favor of . Thats 1 contra, 1 pro. > > > Goba > > > > > > Jeroen van Wolffelaar > [EMAIL PROTECTED] > http://www.A-Eskwadraat.nl/~jeroen > >
[PHP-DOC] cvs: phpdoc /en/functions java.xml
danbeck Tue Jun 26 16:08:25 2001 EDT Modified files: /phpdoc/en/functionsjava.xml Log: additional grammer correction Index: phpdoc/en/functions/java.xml diff -u phpdoc/en/functions/java.xml:1.4 phpdoc/en/functions/java.xml:1.5 --- phpdoc/en/functions/java.xml:1.4Tue Jun 26 06:25:28 2001 +++ phpdoc/en/functions/java.xmlTue Jun 26 16:08:25 2001 @@ -4,12 +4,12 @@ There are two possible ways to bridge PHP and Java: you can either -integrate Java into PHP or, which is the more stable and efficient -solution, integrate PHP into a Java Servlet environment. +integrate Java into PHP, which is the more stable and efficient +solution, or integrate PHP into a Java Servlet environment. The former is provided by ext/java, the latter by a SAPI module that interfaces with the Servlet server. - + PHP 4 ext/java provides a simple and effective means for creating and invoking methods on Java objects from PHP. The JVM is created using JNI, and everything runs in-process. Build instructions for ext/java can be
[PHP-DOC] cvs: phpdoc /en/language types.xml
jeroen Tue Jun 26 14:46:26 2001 EDT Modified files: /phpdoc/en/language types.xml Log: Warned for a bug in the scripting engine. (implicite casting on negative overflow, bug#11685) Index: phpdoc/en/language/types.xml diff -u phpdoc/en/language/types.xml:1.29 phpdoc/en/language/types.xml:1.30 --- phpdoc/en/language/types.xml:1.29 Wed Jun 20 23:46:03 2001 +++ phpdoc/en/language/types.xmlTue Jun 26 14:46:26 2001 @@ -334,6 +334,16 @@ // output: float(500) + + +Unfortunately, there is a bug in the script engine (still present in + 4.0.6, probably resolved in 4.0.7) so that this does not always work + correctly when there are negative numbers involved. However when both + operands are positive, there is no problem. For example: when you do + -5 * $million, the result will be + -429496728. + +
[PHP-DOC] cvs: phpdoc /en/language control-structures.xml
jeroen Tue Jun 26 14:32:47 2001 EDT
Modified files:
/phpdoc/en/language control-structures.xml
Log:
Noted that alternative syntax is deprecated.
if:
statements
else:
bla
endif;
I read that somewhere, but don't recall where :(
Index: phpdoc/en/language/control-structures.xml
diff -u phpdoc/en/language/control-structures.xml:1.29
phpdoc/en/language/control-structures.xml:1.30
--- phpdoc/en/language/control-structures.xml:1.29 Tue May 22 01:16:31 2001
+++ phpdoc/en/language/control-structures.xml Tue Jun 26 14:32:47 2001
@@ -38,7 +38,7 @@
than $b:
-if ($a > $b)
+if ($a > $b)
print "a is bigger than b";
@@ -54,7 +54,7 @@
$a into $b:
-if ($a > $b) {
+if ($a > $b) {
print "a is bigger than b";
$b = $a;
}
@@ -84,7 +84,7 @@
than b otherwise:
-if ($a > $b) {
+if ($a > $b) {
print "a is bigger than b";
} else {
print "a is NOT bigger than b";
@@ -119,7 +119,7 @@
or a is smaller than b:
-if ($a > $b) {
+if ($a > $b) {
print "a is bigger than b";
} elseif ($a == $b) {
print "a is equal to b";
@@ -152,6 +152,18 @@
Alternative syntax for control structures
+
+
+
+ Alternative syntax is deprecated as of PHP 4. Basically,
+ it just generates unreadable code, and it gets
+ very complicated when mixing it with the normal syntax.
+ Although there are no plans to break this syntax, it
+ cannot be ruled out that one day this will stop working.
+ You are warned.
+
+
+
PHP offers an alternative syntax for some of its control
structures; namely, if,
[PHP-DOC] cvs: phpdoc /ja/chapters config.xml install.xml /ja/functions array.xml info.xml mbstring.xml
hirokawaTue Jun 26 14:20:35 2001 EDT
Modified files:
/phpdoc/ja/chapters config.xml install.xml
/phpdoc/ja/functionsarray.xml info.xml mbstring.xml
Log:
translation update. fixed parser error about zlib.
Index: phpdoc/ja/chapters/config.xml
diff -u phpdoc/ja/chapters/config.xml:1.11 phpdoc/ja/chapters/config.xml:1.12
--- phpdoc/ja/chapters/config.xml:1.11 Thu Apr 5 17:09:15 2001
+++ phpdoc/ja/chapters/config.xml Tue Jun 26 14:20:34 2001
@@ -783,34 +783,34 @@
拡張ロード命令
-
-
- enable_dl
- 論理値
-
-
-
+
+
+ enable_dl
+ 論理値
+
+
+
この命令は、Apache モジュール版の PHP
を使用した場合にのみ
有用です。
PHP の動的ロード拡張機能を dl で
仮想サーバー毎またはディレクトリ毎にオンまたはオフに変更することが
できます。
-
-
+
+
動的ロード機能をオフにするのは主としてセキュリティ上の理由によります。
動的ロード機能により、
safe_mode および open_basedir の拘束を全て無視することが
可能になります。
-
-
+
+
デフォルトでは、セーフモードを使用している場合以外、
動的ロードが可能です。
セーフモードにおいては、dl
を使用することが常に不可能になります。
-
-
-
-
+
+
+
+
extension_dir
@@ -1189,7 +1189,7 @@
クライアントライブラリのメッセージは、警告としてレポートされます。
この値は、スクリプトから
sybase_min_client_severity をコールする
-ことによりセットすることづϯ能です。
+ことによりセットすることづ?能です。
デフォルトは 10
であり、効率的にレポートを抑制して行うようにしています。
Index: phpdoc/ja/chapters/install.xml
diff -u phpdoc/ja/chapters/install.xml:1.31 phpdoc/ja/chapters/install.xml:1.32
--- phpdoc/ja/chapters/install.xml:1.31 Sun Jun 3 02:51:42 2001
+++ phpdoc/ja/chapters/install.xml Tue Jun 26 14:20:34 2001
@@ -2341,18 +2341,16 @@
-
+
- --with-zziplib[=DIR]
+ --with-zip[=DIR]
-PHP 4: ZZIPlibサポートを有効にします。(ZZIPlib >= 0.10.6が
-必要) DIR は、ZZIPlib
をインストールしたディレクトリで、デフォ
-ルトは、/usr/localです。
+PHP 4: zipサポートを有効にします。(zziplib >= 0.10.6が必要)
+DIRは、zziplib
+をインストールしたディレクトリで、デフォルトは
+/usr/localです。
- ZZIPlib の最新版は、&url.zziplib;にあります。
Index: phpdoc/ja/functions/array.xml
diff -u phpdoc/ja/functions/array.xml:1.27 phpdoc/ja/functions/array.xml:1.28
--- phpdoc/ja/functions/array.xml:1.27 Sun Jun 24 09:06:31 2001
+++ phpdoc/ja/functions/array.xml Tue Jun 26 14:20:35 2001
@@ -1789,17 +1789,17 @@
説明
- end
+ mixed end
array array
endはarrayの内部ポイ
- ンタを最後の要素まで進めます。
+ ンタを最後の要素まで進め、その要素を返します。
current, each,
- end, next ,
+ next ,
resetも参照下さい。
Index: phpdoc/ja/functions/info.xml
diff -u phpdoc/ja/functions/info.xml:1.24 phpdoc/ja/functions/info.xml:1.25
--- phpdoc/ja/functions/info.xml:1.24 Sun Jun 3 02:51:43 2001
+++ phpdoc/ja/functions/info.xmlTue Jun 26 14:20:35 2001
@@ -6,7 +6,7 @@
assert
-assertion が false であるかどうかを調べる
+assertion が FALSE であるかどうかを調べる
説明
@@ -19,7 +19,7 @@
assert は、指定した
assertionを調べて、結果が
- falseの場合に適当な動作をします。
+ FALSEの場合に適当な動作をします。
assertion が文字列として指定された場合、
@@ -31,7 +31,7 @@
assertion は、デバッグ目的にのみ使用するべきです。
- assertion
を常にtrueとなる条件を調べる故障診断に使用し、trueでな
+ assertion
+を常にTRUEとなる条件を調べる不具合診断に使用し、TRUEでな
い場合に何らかのプログラミングエラーを示したり、extension
関数ま
たは特定のシステム制限や機能といった特定の機能の存在をチェックす
るために使用することが可能です。
@@ -122,7 +122,7 @@
assert_options は、指定したオプションの元の
- 設定値またはエラーの場合にfalseを返します。
+ 設定値またはエラーの場合にFALSEを返します。
@@ -142,7 +142,7 @@
name
で指定する拡張機能がロードされている
- 場合に true を返します。phpinfo を用いて種々
+ 場合にTRUEを返します。phpinfo
+を用いて種々
の拡張機能の名前を知ることができます。
@@ -192,7 +192,7 @@
varname が示す環境変数の値を返し、
- エラーの場合は false を返します。
+ エラーの場合はFALSEを返します。
$ip = getenv("REMOTE_ADDR"); // ユーザーのIPアドレスを得ます
@@ -229,7 +229,7 @@
varname で指定された PHP 設定オプション
- の現在の値を返し、エラーの場合は FALSE を返します。
+
+の現在の値を返し、エラーの場合はFALSEを返します。
この関数は、
@@ -338,7 +338,7 @@
現在のページが最後に更新された時刻を返します。返される
値は Unix のタイムスタンプで、そのまま date
- に渡す事ができます。エラーの場合は FALSE
を返します。
+
+に渡す事ができます。エラーの場合はFALSEを返します。
getlastmodの例
@@ -371,7 +371,7 @@
- 現在のスクリプトの i ノードを返し、エラーの場合は FALSE
を返しま
+
+現在のスクリプトのiノードを返し、エラーの場合はFALSEを返しま
す。
@@ -397,7 +397,7 @@
- 現在の PHP のプロセス ID を返し、エラーの場合は FALSE
を返します。
+ 現在の PHP のプロセス ID
+を返し、エラーの場合はFALSEを返します。
@@ -494,7 +494,7 @@
- 設定オプションの値を変更し、失敗した際に
false、
+ 設定オプションの値を変更し、失敗した際に
+FALSE、
成功時にその設定オプションの元の値を返します。
@@ -525,7 +525,7 @@
成功時に設定オプションの値を返し、失敗時に
- false を返します。
+ FALSE を返します。
ini_alter,
@@
[PHP-DOC] cvs: phpdoc /en/functions info.xml
zak Tue Jun 26 13:24:50 2001 EDT Modified files: /phpdoc/en/functionsinfo.xml Log: assert() Corrected minor grammatical and spelling mistakes Added information on assert callback functions Added an example of a callback function Index: phpdoc/en/functions/info.xml diff -u phpdoc/en/functions/info.xml:1.50 phpdoc/en/functions/info.xml:1.51 --- phpdoc/en/functions/info.xml:1.50 Mon Jun 25 15:39:59 2001 +++ phpdoc/en/functions/info.xmlTue Jun 26 13:24:50 2001 @@ -1,7 +1,7 @@ PHP options & information PHP options/info - + assert @@ -16,38 +16,83 @@ - assert will check the given - assertion and take appropriate + assert will check the given + assertion and take appropriate action if its result is FALSE. If the assertion is given as a string it will be evaluated as PHP code by assert. - The advantages of a string assertion + The advantages of a string assertion are less overhead when assertion checking is off and messages containing the assertion expression when - an assertion failes. + an assertion fails. - Assertion should be used as a debugging feature only. You may + Assertions should be used as a debugging feature only. You may use them for sanity-checks that test for conditions that should always be TRUE and that indicate some programming errors if not or to check for the presence of certain features like extension functions or certain system limits and features. - Assertions should not be used for normal runtime operations + Assertions should not be used for normal runtime operations like input parameter checks. As a rule of thumb your code - should always be able to work correct if assertion checking + should always be able to work correctly if assertion checking is not activated. The behavior of assert may be configured - by assert_options or by .ini-settings + by assert_options or by .ini-settings described in that functions manual page. + +The assert_options function and/or +ASSERT_CALLBACK configuration directive allow a callback +function to be set to handle failed assertions. + + +assert callbacks are particularly +useful for building automated test suites because they +allow you to easily capture the code passed to the +assertion, along with information on where the assertion +was made. While this information can be captured via other +methods, using assertions makes it much faster and easier! + + +The callback function should accept three arguments. The first +argument will contain the file the assertion failed in. The second +arugument will contain the line the assertion failed on and the +third argument will contain the expression that failed (if any - literal +values such as 1 or "two" will not be passed via this argument) + + +Handle a failed assertion with a custom handler + + Assertion Failed: + File '$file'
+ Line '$line'
+ Code '$code'
"; +} + +// Set up the callback +assert_options (ASSERT_CALLBACK, 'my_assert_handler'); + +// Make an assertion that should fail +assert ('mysql_query ("")'); + ?> + + - + @@ -60,7 +105,7 @@ mixed assert_options int what - mixed + mixed value @@ -115,7 +160,7 @@ (null) user function to call on failed assertions - + @@ -123,7 +168,7 @@ setting of any option or FALSE on errors. - + @@ -153,7 +198,7 @@ - + dl @@ -175,7 +220,7 @@ - + getenv @@ -194,7 +239,7 @@ varname, or FALSE on an error. -$ip = getenv ("REMOTE_ADDR"); // get the ip number of the user +$ip = getenv ("REMOTE_ADDR"); // get the ip number of the user @@ -294,7 +339,7 @@ - Returns the current active configuration setting of + Returns the current active configuration setting of magic_quotes_gpc. (0 for off, 1 for on). @@ -317,14 +362,14 @@ Description - long + long get_magic_quotes_runtime - Returns the current active configuration setting of + Returns the current active configuration setting of ma
Re: [PHP-DOC] experimental manual source for advanced translation handling
> i've done some experiments on one of the topics > we had discussed here before the list went down > > all the files in the function directory have been split up > in a general part and a subdirectory containing the actual > refentries, one function refentry per file This sounds like a good idea to me, as you already argue. That the xml processing is slowed down is a pity, but it is IMO not important. It's the output and the ease of modifying /translating that counts, not the number of cycles wasted on it. > i'm not sure yet wether we should follow the way presented > here, which would break CVS history a bit (which is not as > important for documentation as it is for actual code) > or whether it would be better to leave the xml files as > they are and have them split up and recombined in the > background during the actual built, but that is a different > story ... The latter option is IMO best: you do not break CVS, you do not have to change all files, and you can still edit the files in a module-basis, rather than a single file for every minor function. For translation it is less useful, you'll need to get single functions from the english sources when you want to translate a new function, rather than simply copying a file. Jeroen
[PHP-DOC] cvs: phpdoc /en/functions sockets.xml
sniper Tue Jun 26 12:44:10 2001 EDT Modified files: /phpdoc/en/functionssockets.xml Log: Since the PHP_SYSTEM_READ is same as PHP_BINARY_READ it is now removed. Index: phpdoc/en/functions/sockets.xml diff -u phpdoc/en/functions/sockets.xml:1.11 phpdoc/en/functions/sockets.xml:1.12 --- phpdoc/en/functions/sockets.xml:1.11Sun Jun 24 17:27:21 2001 +++ phpdoc/en/functions/sockets.xml Tue Jun 26 12:44:10 2001 @@ -427,17 +427,12 @@ -PHP_SYSTEM_READ - use the system read() +PHP_BINARY_READ - use the system read() (Default in PHP >= 4.0.7) -PHP_BINARY_READ - binary safe read() (same as PHP_READ_SYSTEM) - - - - -PHP_NORMAL_READ - Default. Reading stops at \n or \r. +PHP_NORMAL_READ - reading stops at \n or \r. (Default in PHP <= 4.0.6)
Re: [PHP-DOC] cvs: phpdoc / version.dsl version.xml
> Modified files: > /phpdoc version.dsl version.xml > Log: > official 4.0.6 update >- ((equal-ci? (data nl) "abs") (literal "PHP 3, PHP 4 ")) >+ ((equal-ci? (data nl) "abs") (literal "PHP 3, PHP 4 >= 4.0b1")) Is it really necessary to specify that this function worked as of the first beta? IMO it would be better if you stick with public releases, i.e. 4.0.0, etc, and no beta's or RC's. Those versions are only really used during development. Jeroen
Re: [PHP-DOC] Convention: true/false
> TRUE *is not* a constant. There is a boolean type in PHP 4. > TRUE *was* a constant in PHP 3... It is still defined as constant, just like NULL. (zend_constants.c:117 : true/false constants) THough you can argue that it's better to see it as being a special keyword. It is a constant in the sense that its value never changes. And, though layout shouldn't be an issue when it comes to xml, I like the makeup op better in case of values like true... So, I'm still in favor of . Thats 1 contra, 1 pro. > Goba > > Jeroen van Wolffelaar [EMAIL PROTECTED] http://www.A-Eskwadraat.nl/~jeroen
[PHP-DOC] Bug #11683 Updated: Manual vague on .htaccess options
ID: 11683 Updated by: sniper Reported By: [EMAIL PROTECTED] Old-Status: Open Status: Closed Bug Type: Documentation problem Operating system: PHP Version: 4.0.5 Assigned To: Comments: php_value include_path ".:/some/path/:/next/time/rtfm" --Jani Previous Comments: --- [2001-06-25 22:52:31] [EMAIL PROTECTED] In checking the online manual to find the syntax for setting a local include path for PHP4, it doesn't seem to have that. All it does is suggest that PHP3 options can be added in .htaccess by prefixing with php3_. Does 4 use php_? php3_? Not work with .htaccess? Would help to have this on the configuration page of the manual. --- ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=11683&edit=2
[PHP-DOC] cvs: phpdoc /en/functions mnogosearch.xml
dim Tue Jun 26 10:38:34 2001 EDT Modified files: /phpdoc/en/functionsmnogosearch.xml Log: New UDM_PARAM_VARDIR parameter in Udm_Set_Agent_Param Index: phpdoc/en/functions/mnogosearch.xml diff -u phpdoc/en/functions/mnogosearch.xml:1.14 phpdoc/en/functions/mnogosearch.xml:1.15 --- phpdoc/en/functions/mnogosearch.xml:1.14Tue May 8 17:33:30 2001 +++ phpdoc/en/functions/mnogosearch.xml Tue Jun 26 10:38:34 2001 @@ -1139,7 +1139,6 @@ also to a document this link leads to. It works in SQL database mode and is not supported in built-in database and Cachemode. - Crosswords are supported only in mnoGoSearch 3.1.11 or later. @@ -1147,6 +1146,15 @@ + + + UDM_PARAM_VARDIR - specifies a custom path to directory where indexer stores data +when using built-in database and in cache mode. +By default /var directory of +mnoGoSearch installation is used. Can have only string +values. +The parameter is available in php-4.0.7 or later. + + +
Re: [PHP-DOC] Convention: true/false
> How about the convenstion that true/false should always be written as: > > TRUE > and idem for false? > > It is also possible to make that a snippet, but I think that'd be > overkill... What do you think of it? > > By the way: typical example of where a good script can be used :) In fact > just > a multifile regex of course. > /(<(literal|constant)>)?false()?/i => FALSE for > example. TRUE *is not* a constant. There is a boolean type in PHP 4. TRUE *was* a constant in PHP 3... Goba
Re: [PHP-DOC] I am translating PHP manual in Romanian
> Who should I talk about license and rights ? AFAIK, you don't need to, since your translation will be under the same licence as the current one, i.e. GPL. (there is no LICENCE file in the cvs, I notice now) If you need help about how to do it, see the various readme's in the root of the phpdoc module (accessible via cvs: http://www.php.net/anoncvs.php ) If you have any questions, feel free to mail us, because the more translations the better :). If you already have one or more translated files (xml, that is), please mail them to the list. Eventually you should also request a CVS account to commit the translated files by yourself without needing to bother us ;) Greetz, Jeroen
[PHP-DOC] cvs: phpdoc /en/functions java.xml
sbergmann Tue Jun 26 06:25:28 2001 EDT Modified files: /phpdoc/en/functionsjava.xml Log: -currently Index: phpdoc/en/functions/java.xml diff -u phpdoc/en/functions/java.xml:1.3 phpdoc/en/functions/java.xml:1.4 --- phpdoc/en/functions/java.xml:1.3Fri Jun 22 22:34:00 2001 +++ phpdoc/en/functions/java.xmlTue Jun 26 06:25:28 2001 @@ -4,8 +4,8 @@ There are two possible ways to bridge PHP and Java: you can either -integrate Java into PHP or, which is the more currently stable and -efficient solution, integrate PHP into a Java Servlet environment. +integrate Java into PHP or, which is the more stable and efficient +solution, integrate PHP into a Java Servlet environment. The former is provided by ext/java, the latter by a SAPI module that interfaces with the Servlet server.
[PHP-DOC] cvs: phpdoc /en/functions info.xml
damsMon Jun 25 15:39:59 2001 EDT
Modified files:
/phpdoc/en/functionsinfo.xml
Log:
Adding some details about putenv and safe mode (from php.ini).
Index: phpdoc/en/functions/info.xml
diff -u phpdoc/en/functions/info.xml:1.49 phpdoc/en/functions/info.xml:1.50
--- phpdoc/en/functions/info.xml:1.49 Mon Jun 25 15:01:14 2001
+++ phpdoc/en/functions/info.xmlMon Jun 25 15:39:59 2001
@@ -31,7 +31,7 @@
Assertion should be used as a debugging feature only. You may
use them for sanity-checks that test for conditions that should
- always be TRUE and that indicate some programming errors if not
+ always be TRUE and that indicate some programming errors if
+not
or to check for the presence of certain features like extension
functions or certain system limits and features.
@@ -139,7 +139,7 @@
- Returns TRUE if the extension identified by
+ Returns TRUE if the extension identified by
name is loaded. You can see the names of
various extensions by using phpinfo.
@@ -191,8 +191,7 @@
Returns the value of the environment variable
- varname, or FALSE on an error.
-
+ varname, or FALSE on an error.
$ip = getenv ("REMOTE_ADDR"); // get the ip number of the user
@@ -203,9 +202,8 @@
You can see a list of all the environmental variables by using
phpinfo. You can find out what many of them
mean by taking a look at the CGI
- specification, specifically the page on
- environmental variables.
+ specification, specifically the page on
+ environmental variables.
This function does not work in ISAPI mode.
@@ -236,7 +234,7 @@
Returns the current value of the PHP configuration variable
- specified by varname, or FALSE if an error
+ specified by varname, or FALSE if an
+error
occurs.
@@ -353,7 +351,7 @@
Returns the time of the last modification of the current
page. The value returned is a Unix timestamp, suitable for
- feeding to date. Returns FALSE on error.
+ feeding to date. Returns FALSE on error.
getlastmod() example
@@ -386,7 +384,7 @@
- Returns the current script's inode, or FALSE on error.
+ Returns the current script's inode, or FALSE on error.
See also getmyuid,
@@ -416,7 +414,7 @@
- Returns the current PHP process ID, or FALSE on error.
+ Returns the current PHP process ID, or FALSE on error.
@@ -448,7 +446,7 @@
- Returns the user ID of the current script, or FALSE on error.
+ Returns the user ID of the current script, or FALSE on error.
See also getmypid,
@@ -1265,8 +1263,26 @@
Adds setting to the server environment. The
-environment variable will only exist for the duration of the current request.
-At the end of the request the environment is restored to its original state.
+ environment variable will only exist for the duration of the current
+ request. At the end of the request the environment is restored to
+ its original state.
+
+
+ Setting certain environment variables may be a potential security breach.
+ The safe_mode_allowed_env_vars directive contains a
+ comma-delimited list of prefixes. In Safe Mode, the user may only
+ alter environment variables whose names begin with the prefixes
+ supplied by this directive. By default, users will only be able
+ to set environment variables that begin with PHP_
+ (e.g. PHP_FOO=BAR). Note: if this directive is empty,
+ PHP will let the user modify ANY environment variable!
+
+
+ The safe_mode_protected_env_vars directive
+ contains a comma-delimited list of environment variables, that
+ the end user won't be able to change using putenv.
+ These variables will be protected even if
+safe_mode_allowed_env_vars
+ is set to allow to change them.
@@ -1425,7 +1441,8 @@
- See also: get_loaded_extensions.
+ See also
+ get_loaded_extensions.
[PHP-DOC] Bug #11683: Manual vague on .htaccess options
From: [EMAIL PROTECTED] Operating system: Linux PHP version: 4.0.5 PHP Bug Type: Documentation problem Bug description: Manual vague on .htaccess options In checking the online manual to find the syntax for setting a local include path for PHP4, it doesn't seem to have that. All it does is suggest that PHP3 options can be added in .htaccess by prefixing with php3_. Does 4 use php_? php3_? Not work with .htaccess? Would help to have this on the configuration page of the manual. -- Edit Bug report at: http://bugs.php.net/?id=11683&edit=1
