>It's not clear to me that inline comments were outright rejected here. >Perhaps I missed some other discussion but to my biased eye the >general concensus was favourable.
I remember several situations where Adrian and Jacob rejected an inline comment syntax (IRC, tickets, group). I found one directly in the ticket system: http://code.djangoproject.com/ticket/648 That's why I said "shot down often enough to stop the discussion". Even though it might be neat to vote on something, at least it should be a something where the core devs didn't outright dump the idea earlier on. Or if it is, at least bring new arguments to the table that address their complaints ;-) I myself am -0 on inline comment syntax. Reason: comments in templates just don mix up for me. I don't see much reason in putting _template_ comments in there, except as blocks - and in those cases there is already the {% comment %} syntax. For other cases web designers will much more naturally use HTML comments, as that's the syntax they already know about. Actually comments that don't show up in the generated HTML aren't really that useful for design, anyways: as templates do generate HTML, and that HTML is quite complex, you _want_ your comments to show up in the result, so you can use them as landmarks in the source view. Actually the only reason I see for {% comment %} at all is to disable a block of template code - and therefore I would actually prefer it to be renamed to {% disable %} :-) bye, Georg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
