News for hackers. Stuff that matters.

A comment on Proposal: Hack Free CSS with the @unsupported Directive. Parent comment

Re:Proposal: Hack Free CSS with the @unsupported Directive by generalk on Monday October 19, 2009 @02:01PM (#890563)
Well, sure, that takes care of the symptom but not the underlying issue: comments shouldn't affect runtime! To put it differently, if I remove all comments from a source file, the compiled/interpreted result should be 100% the same. If it isn't, something's wrong.
[ Parent | on HN ]
Re:Proposal: Hack Free CSS with the @unsupported Directive by chriseppstein on Monday October 19, 2009 @02:21PM (#890617)
In this case, the something wrong is that the specification didn't have the foresight to create a syntax robust enough to support actually upgrading the spec for real users. Discarding unrecognized syntax is a nice, robust behavior, but it doesn't cut it.
[ Parent | on HN ]
Re:Proposal: Hack Free CSS with the @unsupported Directive by knome on Monday October 19, 2009 @06:11PM (#891198)
By this syntax they aren't comments anymore.
[ Parent | on HN ]