​Folks,  one more thing to consider: the next big release of yaql (1.0,
coming really soon) will get support of curly brac​es (by default - to
initialise dictionaries in the following way:

v0.2/v0.3 syntax: dict(key1=>value1, key2=>value2)

v1 syntax: {key1=>value1, key2=>value2} (the old syntax works in v1 as well)


So, {} will become a valid yaql expression (empty dict). I believe it is
not a big deal to parse that correctly and differentiate between outer
markup and an expression contained within, however statements like <{{}}>
may be a little ugly.

--
Regards,
Alexander Tivelkov

On Thu, Feb 19, 2015 at 1:13 PM, Nikolay Makhotkin <nmakhot...@mirantis.com>
wrote:

> Hi !
>
> From those three I'd choose only <{ ... }>, it looks better for YAML while
> '%' sign looks foreign for YAML. Moreover, it needs extra spaces for
> writing expressions:
>
> Compare:
> 1. <%$.var + 1%>
> 2. <% $.var + 1 %>
> 3. <{$.var + 1}>
>
> One more point from me: We can't do things just beacuse it is familiar
> with N things and it should be so.
>
>
> Best Regards,
> Nikolay
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to