All the other IF* tags have else clause, I see no reason why ifchanged
should be alone without it.

I say +1 for consistency

On 6/11/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> I don't want to start an opening/closing battle in Trac, so I'll bring
> this up here: I'm almost convinced by the use case for adding "else" to
> "ifchanged" in #4534.
>
> It's admittedly very borderline and on another day I could see myself
> saying this is programming with templates. But for some reason (even if
> only just because I'm fickle and unpredictable), this one seems valid.
> Anybody else who isn't James or SmileyChris (since they've spoken in the
> tickets) got a strong opinion either way?
>
> Malcolm
>
>
> >
>


-- 
Honza Kr�l
E-Mail: [EMAIL PROTECTED]
ICQ#:   107471613
Phone:  +420 606 678585

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to