I believe that's a great argument for not including the template *source*
in the description. A template instance can encapsulate `vsprintf()`, for
example, and there's never going to be a file or a path resolution. This is
all implementation detail that can be handled via IoC.
$template = new PrintfTemplate('Hello, %1$s!');
$context = new DataObject(['Xedin']);
$greeting = $template->render($context); // Hello, Xedin!
On Monday, September 25, 2017 at 8:15:27 AM UTC+2, Nicolas Grekas wrote:
>
> > Granted, the majority of template engines use a template file-name and a
> set of name/value pairs
>
> Twig also doesn't reference templates by file name.
> It references them by logical name instead, and uses loaders to resolve
> that to whatever storage you'd like to use for the template strings.
>
>
--
You received this message because you are subscribed to the Google Groups "PHP
Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/php-fig/c9192cc6-281e-44e7-98cc-ba2b5c1683c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
