2008-06-25 01:10:51 +00:00
|
|
|
Core.LexerImpl
|
|
|
|
|
TYPE: mixed/null
|
|
|
|
|
VERSION: 2.0.0
|
|
|
|
|
DEFAULT: NULL
|
|
|
|
|
--DESCRIPTION--
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
This parameter determines what lexer implementation can be used. The
|
|
|
|
|
valid values are:
|
|
|
|
|
</p>
|
|
|
|
|
<dl>
|
|
|
|
|
<dt><em>null</em></dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Recommended, the lexer implementation will be auto-detected based on
|
|
|
|
|
your PHP-version and configuration.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt><em>string</em> lexer identifier</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
This is a slim way of manually overridding the implementation.
|
|
|
|
|
Currently recognized values are: DOMLex (the default PHP5
|
|
|
|
|
implementation)
|
|
|
|
|
and DirectLex (the default PHP4 implementation). Only use this if
|
|
|
|
|
you know what you are doing: usually, the auto-detection will
|
|
|
|
|
manage things for cases you aren't even aware of.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt><em>object</em> lexer instance</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Super-advanced: you can specify your own, custom, implementation that
|
|
|
|
|
implements the interface defined by <code>HTMLPurifier_Lexer</code>.
|
|
|
|
|
I may remove this option simply because I don't expect anyone
|
|
|
|
|
to use it.
|
|
|
|
|
</dd>
|
|
|
|
|
</dl>
|
2008-12-06 09:24:59 +00:00
|
|
|
--# vim: et sw=4 sts=4
|
