]>
Commit | Line | Data |
---|---|---|
d4949327 NL |
1 | Core.LexerImpl\r |
2 | TYPE: mixed/null\r | |
3 | VERSION: 2.0.0\r | |
4 | DEFAULT: NULL\r | |
5 | --DESCRIPTION--\r | |
6 | \r | |
7 | <p>\r | |
8 | This parameter determines what lexer implementation can be used. The\r | |
9 | valid values are:\r | |
10 | </p>\r | |
11 | <dl>\r | |
12 | <dt><em>null</em></dt>\r | |
13 | <dd>\r | |
14 | Recommended, the lexer implementation will be auto-detected based on\r | |
15 | your PHP-version and configuration.\r | |
16 | </dd>\r | |
17 | <dt><em>string</em> lexer identifier</dt>\r | |
18 | <dd>\r | |
19 | This is a slim way of manually overridding the implementation.\r | |
20 | Currently recognized values are: DOMLex (the default PHP5\r | |
21 | implementation)\r | |
22 | and DirectLex (the default PHP4 implementation). Only use this if\r | |
23 | you know what you are doing: usually, the auto-detection will\r | |
24 | manage things for cases you aren't even aware of.\r | |
25 | </dd>\r | |
26 | <dt><em>object</em> lexer instance</dt>\r | |
27 | <dd>\r | |
28 | Super-advanced: you can specify your own, custom, implementation that\r | |
29 | implements the interface defined by <code>HTMLPurifier_Lexer</code>.\r | |
30 | I may remove this option simply because I don't expect anyone\r | |
31 | to use it.\r | |
32 | </dd>\r | |
33 | </dl>\r | |
34 | --# vim: et sw=4 sts=4\r |