On 3/14/06, hugo <[EMAIL PROTECTED]> wrote:
>
> >{% endif %}{# endif start_process #}
>
> Ugh, no. Sorry, but I am definitely -1 on this.
>
> If we want something useful, go for the {% if something %} ... {% endif
> something %} where the "something" on the endif is optional and if it
> is given, must match the corresponding if. Everything else is just
> silly, because it's either just inline comments (which were shot down
> often enough that discussion about it should stop now) or irritating
> (in the case of not-checked stuff after endif).
>
> This "if blah"/"endif blah" is quite common in other languages, so even
> though I am not a big fan of it, I see that especially in more complex
> templates it would help designers to see where they went wrong in the
> cascading IFs, so I think it would be good to have at least optionally.
>
> bye, Georg
>
I don't think so. In many cases we are talking about html format
output, and spaces is not very important. So you can still using
indent to match the if and endif, just like:
{% if something %}
{% if something %}
{% endif %}
{% endif %}
And if we forget some endif, I think template parser shoud check it
out and complain it for us. So I think {% endif something %} in here
just used for comments. And why shoud we match it with {% if something
%}. And the proposal is also want comment but not syntax check I
think. And {# comment #} is a shortcut for comment tag, I like it.
--
I like python!
My Blog: http://www.donews.net/limodou
NewEdit Maillist: http://groups.google.com/group/NewEdit
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers
-~----------~----~----~----~------~----~------~--~---
