I'm not sure this is actually a problem... mixin definitions aren't actually ambiguous with attributes beginning with -. Attributes can never be at the root of a document, and mixins must be. It shouldn't be hard to add a check for that.
There are a couple of issues with just using CSS selectors. It'll create random selectors sitting around the CSS that aren't actually applied to anything in the document (or, worse, are accidentally applied). Then there's the question of how to handle p color: blue div p font-weight: bold #sidebar +div p Does that add both the color attribute and the font-weight attribute? If so, that requires that we actually resolve CSS selectors to some extent which is tricky and bug-prone. If not, It may break people's expectations. Mislav Marohnić wrote: > Why not make any selector a mixin: > > .floating > :float left > > #content .tag > +.floating > > #footer .info > +#content .tag > color: gray > > If this is too wild, my +1 on the $ char. > > > On Thu, Apr 10, 2008 at 5:36 PM, Garry Hill <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > Consequently I have a patch to change that char from '-' to '$' > > > > http://pastie.org/178566 > > Just realised I didn't update the docs. > > Let me know if you think this '$' version is acceptable and I'll make > a complete patch, including the docs. > > g > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
