for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
/**
* PHPTAL templating engine
*
* PHP Version 5
* @category HTML
* @package PHPTAL
* @author Laurent Bedubourg <[email protected]>
* @author Kornel Lesiński <[email protected]>
* @license http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License
* @version SVN: $Id$
* @link http://phptal.org/
*/
* You can implement this interface to create custom tales modifiers
* Methods suitable for modifiers must be static.
* @subpackage Php
interface PHPTAL_Tales
You can fix this by adding a namespace to your class:
namespace YourVendor; class YourClass { }
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.
{
}
* translates TALES expression with alternatives into single PHP expression.
* Identical to phptal_tales() for singular expressions.
* Please use this function rather than PHPTAL_Php_TalesInternal methods.
* @see PHPTAL_Php_TalesInternal::compileToPHPExpressions()
* @return string
function phptal_tale($expression, $nothrow=false)
return PHPTAL_Php_TalesInternal::compileToPHPExpression($expression, $nothrow);
* returns PHP code that will evaluate given TALES expression.
* e.g. "string:foo${bar}" may be transformed to "'foo'.phptal_escape($ctx->bar)"
* Expressions with alternatives ("foo | bar") will cause it to return array
* Use phptal_tale() if you always want string.
* @param bool $nothrow if true, invalid expression will return NULL (at run time) rather than throwing exception
* @return string or array
function phptal_tales($expression, $nothrow=false)
return PHPTAL_Php_TalesInternal::compileToPHPExpressions($expression, $nothrow);
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.