| 1. | You can deal with name clashes in other ways
您可以采用其他方式解决名称冲突的问题。 |
| 2. | If doing so would cause a name clash , signal a conflict and ask the user what to do
如果这样做会导致命名冲突，标记冲突，告诉用户怎样做。 |
| 3. | First , we needed to change the prefix for the parser from " yy " to something unique in order to avoid name clashes
首先，需要将语法分析器的前缀由" yy "更改成独特的名称，以避免名称冲突。 |
| 4. | This is primarily to avoid name clashes : if two classes have the same attribute and are mapped to global names , they may conflict
这样做主要是为了避免名称冲突：如果两个类具有相同的属性，映射为全局名可能会造成冲突。 |
| 5. | Try to think as hard as possible about future developments for your xml design and be decisive about whether to deal with name clashes , and how to do so
设想一下xml设计以后开发的难度，决定是否要处理名称冲突以及如何处理。 |
| 6. | Mixins may have persistent fields , but currently , this is not implemented perfectly ( there is a potential for a name clash between a mixin and the component or another mixin )
混合组件可以有持久化属性，但是目前，这没有完全被实现（混合组件和组件或和其他混合组件可能存在命名冲突） 。 |
| 7. | To reduce ( but not eliminate ) the potential for name clashes , the convention is to prefix names of non - standard track with a few letters to localize the changes to your organization
要减少（但不是消除）潜在的名称冲突，通常是在非标准路径名前增加几个字母的前缀来定位您组织名的改变。 |
