嵌套类型

  • 网络Nested Type;enclosing type
嵌套类型嵌套类型
  1. 如果type声明为公共类型且不是嵌套类型,则为true;否则为false。

    True if the type is declared public and is not a nested type ; otherwise , false .

  2. 否则将会导致一个编译时间错误,如“该嵌套类型Person无法隐藏封闭类型”。

    You will have a compile-time error something like : " The nested type Person cannot hide an enclosing type " .

  3. 封闭类型{0}必须在嵌套类型之前创建。

    Enclosing type { 0 } must be created before the nested type .

  4. 同一体中的嵌套类型也可以访问那些私有成员。

    Nested types in the same body can also access those private members .

  5. 如果需要由客户端代码实例化类型,则不要使用嵌套类型。

    Do not use nested types if they need to be instantiated by client code .

  6. 避免公开显露嵌套类型。

    Avoid publicly exposed nested types .

  7. 添加新的嵌套类型。

    Adding a new nested type .

  8. 如果可能在声明类型的外部引用类型,则不要使用嵌套类型。

    Do not use nested types if the type is likely to be referenced outside of the declaring type .

  9. 可以使得嵌套类型信息在过程调用图中进行传播。

    By integrating information into traditional interprocedural analysis , the nesting type information of procedures is propagated along call graphs .

  10. 通常情况下,在使用“编辑并继续”时,不能在中断模式下更改嵌套类型声明。

    In general , you cannot make changes to nested type declarations in break mode while using edit and continue .

  11. 将这些全局信息与过程内的局部信息结合起来,就可以在编译时刻确定语句的嵌套类型。

    And later translation and optimization phases can bind this global information with local information inside the procedure to determine the nesting types at compiling time .

  12. 然而,通过编译时刻的静态分析可以部分确定指导语句的嵌套类型,这些信息可以用于指导后续的编译与优化。

    However , by compiling time static analysis , nesting type can be partly determined and this information can be passed to other compiling phases to guide later translation and optimizations .

  13. 结果表明,编译时刻的嵌套类型分析可以有效地确定通常的科学与工程计算程序中指导语句的嵌套类型,基于嵌套类型的翻译与优化可以同时减少运行时开销和目标代码长度。

    The results demonstrate that in typical science and engineering workload the nesting type is highly determinable at compiling time , and the application of this information may achieve less runtime overhead and the reduced code size .

  14. 注意:这个特性已经被弃用了,在创建新的消息类型的时候,不应该再使用它&你应该使用嵌套消息类型来代替它。

    Note that this feature is deprecated and should not be used when creating new message types – use nested message types instead .

  15. 这也就是说,存在嵌套的容器类型。

    This means that there are nested container types .