On Sun, Jul 13, 2008 at 3:01 AM, Chris <[EMAIL PROTECTED]> wrote:
>
> Just out of curiosity, is there a reason why the templating constructs
> can't evaluate arbitrary expressions? It seems terribly awkward to me
> that {% if %} can only evaluate variable names, while you need the
> separate operator {% ifequals %} to test for equality, and for some
> reason it doesn't support {% else %}.
>
> I had a very simple use case where I wanted to do something like:
>
> {% if a == 1}blah{% else %}foo{% endif %}
>
> and the closest I can get is:
>
> {% ifequal a 1 %}blah{% endifequal %}{% ifnotequal a 1 %}foo{%
> endifnotequal %}
>
>
ifequal takes an optional else just as if does:
http://www.djangoproject.com/documentation/templates/#ifequal
The general reasons for why the template language does not behave more like
a programming language can be found int the philosophy block here:
http://www.djangoproject.com/documentation/templates/
Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
