mixins

Its several reusable design patterns ( that use mixins ) help you construct solid , powerful stylesheets .

其多种可重用设计模式（使用混入）能够帮助您构造可靠、强大的样式表。

Mixins are allowed to have parameters , just like components .

混合允许有参数，就像组件一样。

This is where a very useful feature comes in : Mixins .

Ruby一个非常有用的特性Mixin可以帮我们完成这方面的工作。

However , there are other significant difficulties with formulating mixins as generic types .

但是，将mixin明确表述为泛型类型时有其它一些明显的困难。

Mixins are classes that are parameterized by their parent class .

mixin是那些由它们的父类参数化的类。

Thus , in Jam , the visitor pattern can 't be used with mixins .

因此，在Jam中，访问者模式不能和mixin一起使用。

Often , mixins are added to a language as an independent language feature , as is done in Jam .

通常，mixin作为独立语言功能部件添加到某种语言中，就象Jam中的那样。

Sass also allows to parameterize Mixins , which adds some extra flexibility .

Sass也允许将混合类型作为参数，使得混合类型的应用更加灵活。

Mixins : allow to extract common groups of properties , name them and then include them in selectors .

混合类型：允许开发者抽象出性质的共同点，然后命名并且加入到选择器中。

But it is appealing , almost seductive , to incorporate mixins as part of a generic type system .

但是合并mixin以作为泛型类型系统的一部分很吸引人，几乎可以说魅力无穷。

Mixins are more useful when addressing cross-browser issues

当解决跨浏览器的问题时，混合类型会更有用

When mixins are formulated as generic classes , the problem of accidental overrides is particularly nasty .

当mixin被明确表述为泛型类时，意外覆盖的问题特别讨厌。

Sass'hand written parser and translator turn Sass into CSS with variable values replacing their references , mixins expanded etc.

Sass的解析器和翻译器将Sass语言翻译成CSS，并且用变量值替换文件中变量的引用以及混合类型等等。

To support mixins through generic types , we need to have run-time representations of the generic type instantiations available .

为了通过泛型类型支持mixin，我们需要获得泛型类型实例化的运行时表示。

No change has been made to Sass'basic function of enhancing stylesheets with variables , operations , nested selectors , and mixins .

Sass使用变量、操作、嵌套选择器（selector）和Mixin来增强样式表，这些基本功能在新版本没有任何改变。

With mixins formulated as generic classes , we always have a handle on the parent class , the type parameter that the class extends .

将mixin明确表述为泛型类，我们就始终有父类的句柄，它是该类继承的类型参数。

Other OCCI resources might also need a mapping , such as some Links and Mixins , which are defined by the OCCI infrastructure model extension .

其他的OCCI资源可能也需要映射，例如某些Link和Mixin，它们是由OCCI基础设施模型扩展所定义。

With Mixins , the class hierarchy stays clean , and you can just mix in ( oh * that 's where the name comes from !) the features you need .

使用Mixin，可以保持类层次的清晰，所要做的只不过是把你需要的功能代码混入进去（嗯，这正是Mixin名字的来由）。

We 'll relate such a formulation of mixins to previous discussions of this powerful language feature , discussing the advantages and disadvantages of adding mixins through generic types .

我们会将这种mixin的表现方式与先前讨论的这种功能强大的语言特性相关联，讨论通过泛型类型添加mixin的优缺点。

Although the concept of mixins has been applied to many languages , Jam is novel in that it introduces mixin-based programming rigorously in the context of a strongly typed language .

尽管mixin的概念已经应用到了许多语言中，但是Jam还是很新颖，因为它在严格类型化的语言上下文中严格引入了基于mixin的编程。

One really big problem that arises with any formulation of mixins is that the method names of a particular mixin may clash with the method names of a potential instantiation of its superclass .

任何mixin公式都会产生一个非常严重的问题：特定mixin的方法名可能与其超类的潜在实例化的方法名冲突。

Sass and LESS are meta-languages meant to simplify and improve the reusability of CSS3 by introducing nesting , variables , inheritance , mixins , and other enhancements .

Sass和LESS是一种元语言，通过引入嵌套、变量、继承、mixin以及其它的强化来简化和提高对CSS3的可重用性。

Jam mixins can be instantiated only on classes ; unlike components in Jiazzi , there is no notion of mixin composition ( however , the Jam team would like to explore such an extension ) .

只能根据类来实例化Jammixin；与Jiazzi中的组件不同的是，Jam中没有mixin组合的概念（但是，Jam团队有意探究这样的扩展）。

This was sometimes called a " mixin " in C + + , though not to be confused with Ruby mixins ( or the Scala mixin , which I 'll discuss in a later article . )

这有时在C++中称为“混合”，与Ruby的混合（或后文中探讨的Scala混合）有所不同。