So are those functions not always available? If so, we should define
when they are and when they aren't.

My main concern is that your addition may be too technical for anyone
but the most advanced PHP users. I'd appreciate it if you could define
this in a less technical manner. 

Thanks,
Erica

> -----Original Message-----
> From: Hartmut Holzgraefe [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 17, 2002 2:29 AM
> To: [EMAIL PROTECTED]
> Subject: [PHP-DOC] cvs: phpdoc /en language-snippets.ent
> 
> hholzgra              Tue Sep 17 05:28:59 2002 EDT
> 
>   Modified files:
>     /phpdoc/en        language-snippets.ent
>   Log:
>   hope this is not as misleading as the old entry ...
> 
> 
> Index: phpdoc/en/language-snippets.ent
> diff -u phpdoc/en/language-snippets.ent:1.30 phpdoc/en/language-
> snippets.ent:1.31
> --- phpdoc/en/language-snippets.ent:1.30      Sun Sep 15 00:45:31 2002
> +++ phpdoc/en/language-snippets.ent   Tue Sep 17 05:28:59 2002
> @@ -1,4 +1,4 @@
> -<!-- $Revision: 1.30 $ -->
> +<!-- $Revision: 1.31 $ -->
> 
>  <!ENTITY warn.experimental '<warning><simpara>This extension is
>  <emphasis>EXPERIMENTAL</emphasis>. The behaviour of this extension --
> @@ -88,7 +88,7 @@
>  <!ENTITY no.config '<para>This extension has no configuration
directives
> defined in &php.ini;.</para>'>
>  <!ENTITY no.resource '<para>This extension has no resource types
> defined.</para>'>
>  <!ENTITY no.constants '<para>This extension has no constants
> defined.</para>'>
> -<!ENTITY no.requirement '<para>These functions are always
> available.</para>'>
> +<!ENTITY no.requirement '<para>No external libraries are needed to
build
> this extension.</para>'>
>  <!ENTITY no.install '<para>There is no installation needed to use
these
>  functions; they are part of the PHP core.</para>'>
> 
> 
> 
> 
> --
> PHP Documentation Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to