This thread is more appropriate for the haml-dev list.
On Wed, Apr 14, 2010 at 11:08 AM, Suno Ano <[email protected]> wrote:
> How would one describe the architecture of Sass?
>
> ,----[ From an earlier post made by Chris ]
> | In Sass 3, Nathan has made the core of what Sass is a lot more
> | technically robust. This has allowed us to get rid of a number of
> | syntactic annoyances like the need to use = or #{} in the most common
> | cases to use SassScript.
> |
> | On top of this core, there are three parsers, one for the indentation
> | based syntax, another for the css superset syntax called scss, and one
> | for parsing css3. The way these parsers work is by translating your
> | document into a syntax agnostic representation called an AST, which can
> | then be converted to css, sass, or scss. This is also what enables the
> | two syntaxes to completely interoperate across imports.
> `----
>
> So the architecture is like this, bottom to top:
>
> - Sass core at the bottom (what exactly is this?); judging from the
> source, a bunch of logic busy with doing conversion and
> imports/exports
> - sitting atop this core are three parsers, one for each syntax,
> translating into AST
> - what else?
>
> How do those components work together? Workflow?
>
>
>
>
>
>
>
>
> --
> 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] <haml%[email protected]>.
> For more options, visit this group at
> http://groups.google.com/group/haml?hl=en.
>
>
--
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.
