> If you're answer for the other contexts is to use a template engine, > why is the answer for this not to use a template engine? > You want to add this because people don't use template engine, > so what makes you think they will use this when there is a valid solution already available?
Because it is almost impossible to add template engine in a big project with PHP templates. But new version of language usually can easily be used. Because this is very frequent operation, and error or inattention with current syntax can cause security problems. Because other filters are task-dependent, not external-context-dependent. Of course, we can have own file format with PHP processing for our tasks, and external context won't be HTML, but then it is task-dependent context. Actually, HTML is also task-dependent external context, and PHP was made (and is used) specially for this task. And because for other context you may need a filter combination, so single operator will not be very useful. But last filter in a chain is our external context, and external context in very many cases is HTML/XML. 2016-07-01 1:42 GMT+05:00 Ryan Pallas <derokor...@gmail.com>: > > > On Thu, Jun 30, 2016 at 1:35 PM, Михаил Востриков < > michael.vostri...@gmail.com> wrote: > >> >> >> - Other people will ask about operator for another context >> And you can say: We already added an operator for the main web context, >> because it is the most frequently used context. If you have a lot of work >> with other contexts, please use template engine. >> >> > If you're answer for the other contexts is to use a template engine, why > is the answer for this not to use a template engine? You want to add this > because people don't use template engine, so what makes you think they will > use this when there is a valid solution already available? >
