I finally agree it sounds like the best

Jacques


Le 15/12/2017 à 11:28, Daniel Dekany a écrit :
OK, so I would go for [=exp] (see the reason told in this thread). How
acceptable is that guys?


Tuesday, December 5, 2017, 11:56:59 AM, Woonsan Ko wrote:

On Mon, Dec 4, 2017 at 10:28 AM, Daniel Dekany <ddek...@apache.org> wrote:
Monday, December 4, 2017, 10:21:48 AM, Taher Alkhateeb wrote:

uh-huh, but I suspect maybe more collisions or need to escape
character in something like [this] or <this> than {{this}}. Anyway,
nothing critical IMO, only thinking out loud.
But they were [=this] and <=this>, so the sequences that will clash
are "[=" and "<=", which are quite rare. Oh wait... "<=" is not rare
at all: "if (x <= y)". But "[=" still is. OK, so I guess at this point
the two competitors left are {{exp}} and [=exp] (regardless of tag
syntax).
+1.00 on [=exp].
+0.49 on {{exp}}.

:-D

Many languages or templates allows ${exp}, including JavaScript. [1]
And, mustache is supported in many languages or templates, too. [2]
Therefore, I think there are more chances using both ${exp} and
{{exp}} in output we want to generate in the future.
The mustache style looks charming at the moment, but I wonder how its
charming can help for the original intention (to avoid any possible
collision in the output we want to generate by an alternative as much
as we can).

Regards,

Woonsan

[1] https://en.wikipedia.org/wiki/String_interpolation
[2] https://mustache.github.io/

On Mon, Dec 4, 2017 at 12:00 PM, Daniel Dekany <ddek...@apache.org> wrote:
Monday, December 4, 2017, 9:17:34 AM, Taher Alkhateeb wrote:

So maybe a safe bet (and a familiar one) is the mustache syntax.

In addition to avoiding clashes it might help with a multi-chained
template. For example, we use FreeMarker extensively in Apache OFBiz
to generate many documents including XML. Now our XML documents might
contain some ${variable} that needs to be interpreted in the XML
parser, not the freemarker parser (without having to escape characters
everywhere)
Though that also works with all the other proposal syntaxes as well.

On Mon, Dec 4, 2017 at 8:50 AM, Jacques Le Roux
<jacques.le.r...@les7arts.com> wrote:
Le 03/12/2017 à 22:06, Woonsan Ko a écrit :
It is also most productive as no shift key is required.
Depends on keyboard, for French keyboard type (azerty) you need to use Alt
key ;)
Same for {{...}} anyway

Jacques

--
Thanks,
  Daniel Dekany

--
Thanks,
  Daniel Dekany


Reply via email to