I agree to a point, but sometimes the comment is a block
of exposition explaining usage philosophy or some such.
I could see a valid argument being made about factoring
that elsewhere, but frankly sometimes a couple of lines of
explanation in the middle of code (even view code) is the
best place when sharing info between you and other programmers
(or future you). Another option I suppose would be converting
them all to the
<%#
#
#
%>
style, as unwieldy as that is.
On the other hand, there are the practical considerations regarding
all the code that currently has this construct, including our
in-house code, various plugins we may have used, etc.
I guess I was initially just wondering though if I had missed
something and inadvertently broken the comment parsing, or
if what I was seeing was really the way it is now.
-glenn
Patrick Crowley wrote:
>> But I'm not yet considering that a valid "fix". Just a symptom.
>
>
> The easiest fix is to not comment out lots of view code. ;)
>
> I generally avoid commenting out view code because it can cause a
> number of problems (code bloat, exposing templates to users, escaping
> issues, etc.).
>
> I'd move this code into a partial. That way, you can include it when
> you need it, and remove it when you don't... without hacks.
>
> -- Patrick
>
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
-~----------~----~----~----~------~----~------~--~---
