PHP_CompatInfo : The Definitive Guide |
If you use the command-line parser with pci script, the solution is a bit different.
To catch cond_code = 1 (function), you must run the command
pci [-inm functions-match.txt]
where functions-match.txt is a text file,
that identify on each line a new condition.
Each blank line or beginning with ; will
be skipped (proceed as comment line like in php.ini)
If first non blank character is an equal sign (=), then you can catch what ever function you want with a preg_match condition (see xdebug example in previous section (web interface)
Example of text file contents
;=^xdebug_
;=alias$
.*
;file_put_contents
![[Caution]](img/admons/caution.png)
|
Caution |
|---|---|
|
Do not confuse a regular expression beginning with equal sign (=), and the same line without =.
In first case you will catch all functions that match the name
pattern given found in all source code, while second case try
to catch only matches found with It's also true for extensions and constants, we will see them now. |
To catch cond_code = 2 (extension), you must run the command
pci [-iem extensions-match.txt]
where extensions-match.txt is a text
file, that identify on each line a new condition.
Each blank line or beginning with ; will
be skipped (proceed as comment line like in php.ini)
If first non blank character is an equal sign (=), then you can catch what ever extension you want with a preg_match condition.
Example of text file contents
;=xdebug
;sqlite
=gd
;=sapi_apache
To catch cond_code = 4 (constant), you must run the command
pci [-icm constants-match.txt]
where constants-match.txt is a text file,
that identify on each line a new condition.
Each blank line or beginning with ; will
be skipped (proceed as comment line like in php.ini)
If first non blank character is an equal sign (=), then you can catch what ever constant you want with a preg_match condition.
Example of text file contents
=PHP_EOL
=DATE_RSS
;FILE_FIND_VERSION
| PHP_CompatInfo : The Definitive Guide | v 1.8.0 : August 1, 2008 |