internals.rst 4.4KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141
  1. Twig Internals
  2. ==============
  3. Twig is very extensible and you can easily hack it. Keep in mind that you
  4. should probably try to create an extension before hacking the core, as most
  5. features and enhancements can be done with extensions. This chapter is also
  6. useful for people who want to understand how Twig works under the hood.
  7. How Twig works?
  8. ---------------
  9. The rendering of a Twig template can be summarized into four key steps:
  10. * **Load** the template: If the template is already compiled, load it and go
  11. to the *evaluation* step, otherwise:
  12. * First, the **lexer** tokenizes the template source code into small pieces
  13. for easier processing;
  14. * Then, the **parser** converts the token stream into a meaningful tree
  15. of nodes (the Abstract Syntax Tree);
  16. * Eventually, the *compiler* transforms the AST into PHP code;
  17. * **Evaluate** the template: It basically means calling the ``display()``
  18. method of the compiled template and passing it the context.
  19. The Lexer
  20. ---------
  21. The lexer tokenizes a template source code into a token stream (each token is
  22. an instance of ``Twig_Token``, and the stream is an instance of
  23. ``Twig_TokenStream``). The default lexer recognizes 13 different token types:
  24. * ``Twig_Token::BLOCK_START_TYPE``, ``Twig_Token::BLOCK_END_TYPE``: Delimiters for blocks (``{% %}``)
  25. * ``Twig_Token::VAR_START_TYPE``, ``Twig_Token::VAR_END_TYPE``: Delimiters for variables (``{{ }}``)
  26. * ``Twig_Token::TEXT_TYPE``: A text outside an expression;
  27. * ``Twig_Token::NAME_TYPE``: A name in an expression;
  28. * ``Twig_Token::NUMBER_TYPE``: A number in an expression;
  29. * ``Twig_Token::STRING_TYPE``: A string in an expression;
  30. * ``Twig_Token::OPERATOR_TYPE``: An operator;
  31. * ``Twig_Token::PUNCTUATION_TYPE``: A punctuation sign;
  32. * ``Twig_Token::INTERPOLATION_START_TYPE``, ``Twig_Token::INTERPOLATION_END_TYPE`` (as of Twig 1.5): Delimiters for string interpolation;
  33. * ``Twig_Token::EOF_TYPE``: Ends of template.
  34. You can manually convert a source code into a token stream by calling the
  35. ``tokenize()`` of an environment::
  36. $stream = $twig->tokenize($source, $identifier);
  37. As the stream has a ``__toString()`` method, you can have a textual
  38. representation of it by echoing the object::
  39. echo $stream."\n";
  40. Here is the output for the ``Hello {{ name }}`` template:
  41. .. code-block:: text
  42. TEXT_TYPE(Hello )
  43. VAR_START_TYPE()
  44. NAME_TYPE(name)
  45. VAR_END_TYPE()
  46. EOF_TYPE()
  47. .. note::
  48. You can change the default lexer use by Twig (``Twig_Lexer``) by calling
  49. the ``setLexer()`` method::
  50. $twig->setLexer($lexer);
  51. The Parser
  52. ----------
  53. The parser converts the token stream into an AST (Abstract Syntax Tree), or a
  54. node tree (an instance of ``Twig_Node_Module``). The core extension defines
  55. the basic nodes like: ``for``, ``if``, ... and the expression nodes.
  56. You can manually convert a token stream into a node tree by calling the
  57. ``parse()`` method of an environment::
  58. $nodes = $twig->parse($stream);
  59. Echoing the node object gives you a nice representation of the tree::
  60. echo $nodes."\n";
  61. Here is the output for the ``Hello {{ name }}`` template:
  62. .. code-block:: text
  63. Twig_Node_Module(
  64. Twig_Node_Text(Hello )
  65. Twig_Node_Print(
  66. Twig_Node_Expression_Name(name)
  67. )
  68. )
  69. .. note::
  70. The default parser (``Twig_TokenParser``) can be also changed by calling the
  71. ``setParser()`` method::
  72. $twig->setParser($parser);
  73. The Compiler
  74. ------------
  75. The last step is done by the compiler. It takes a node tree as an input and
  76. generates PHP code usable for runtime execution of the template.
  77. You can call the compiler by hand with the ``compile()`` method of an
  78. environment::
  79. $php = $twig->compile($nodes);
  80. The ``compile()`` method returns the PHP source code representing the node.
  81. The generated template for a ``Hello {{ name }}`` template reads as follows
  82. (the actual output can differ depending on the version of Twig you are
  83. using)::
  84. /* Hello {{ name }} */
  85. class __TwigTemplate_1121b6f109fe93ebe8c6e22e3712bceb extends Twig_Template
  86. {
  87. protected function doDisplay(array $context, array $blocks = array())
  88. {
  89. // line 1
  90. echo "Hello ";
  91. echo twig_escape_filter($this->env, $this->getContext($context, "name"), "ndex", null, true);
  92. }
  93. // some more code
  94. }
  95. .. note::
  96. As for the lexer and the parser, the default compiler (``Twig_Compiler``) can
  97. be changed by calling the ``setCompiler()`` method::
  98. $twig->setCompiler($compiler);