Open Power Template 2.x family
PLEASE PROVIDE THE TEMPLATES AND/OR PHP CODE IN THE TASK DESCRIPTION (Not URL-s to them). THAT ALLOWS US TO REPRODUCE THE PROBLEM! OTHERWISE WE ARE NOT ABLE TO HELP YOU!
Remember to hide all the security-related pieces of code from the task description, like passwords, server paths etc. for your own safety. Once we close the task, we cannot edit it anymore!
PLEASE PROVIDE THE TEMPLATES AND/OR PHP CODE IN THE TASK DESCRIPTION (Not URL-s to them). THAT ALLOWS US TO REPRODUCE THE PROBLEM! OTHERWISE WE ARE NOT ABLE TO HELP YOU!
Remember to hide all the security-related pieces of code from the task description, like passwords, server paths etc. for your own safety. Once we close the task, we cannot edit it anymore!
FS#75 - Creating new expression parsers
Attached to Project:
Open Power Template
Opened by Zyx (Zyx) - Thursday, 09 April 2009, 02:10 GMT-7
Last edited by Zyx (Zyx) - Thursday, 01 October 2009, 06:53 GMT-7
Opened by Zyx (Zyx) - Thursday, 09 April 2009, 02:10 GMT-7
Last edited by Zyx (Zyx) - Thursday, 01 October 2009, 06:53 GMT-7
|
DetailsCurrently, the expression parser is hard-coded in the template compiler. In order to allow the modularization of this item, there should be created a new base class: Opt_Compiler_Expression. This will allow to create the new expression engines and easier support for the existing ones which are currently hard-coded in the template parser and instruction attribute extractor.
The compileExpression() method should remain, because it can handle the expression type detection. |
This task depends upon