Many people completely ignore the output of the compiler itself, and only
look at the page. This is especially true when using --watch, but can also
happen with --update (e.g. when it's hooked up to a text editor's "compile"
button, or when using something like live-refresh). In this case, it's very
useful to have error reporting in the webpage that the user is viewing.

What's your use case for having sass --update be idempotent?

On Sun, Aug 15, 2010 at 12:14 PM, bitbowl <[email protected]> wrote:

> Excuse my ignorance, but what's the benefit of having compilation
> errors in the generated css?
>
> IMHO idempotent behavior is an essential requirement of compilers to
> assert clean builds. Even if haml/sass have been designed differently
> -- how hard would it be to enforce strict error handling for this
> great tool?
>
> thanks,
> --bb
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" 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/haml?hl=en.

Reply via email to