zoukankan      html  css  js  c++  java
  • "default" Keyword: An Interesting Statement

    I noticed an interesting statement when skimming through Windows Workflow Foundation Hands-On Lab code, it looks like:

    public int amount = default(System.Int32);

    Now I feel a little bit not comfortable  with the "default" here. Look it up (from MSDN):

    In generic classes and methods, one issue that arises is how to assign a default value to a parameterized type T when you do not know the following in advance:

    • Whether T will be a reference type or a value type.

    • If T is a value type, whether it will be a numeric value or a struct.

    Given a variable t of a parameterized type T, the statement t = null is only valid if T is a reference type and t = 0 will only work for numeric value types but not for structs. The solution is to use the default keyword, which will return null for reference types and zero for numeric value types. For structs, it will return each member of the struct initialized to zero or null depending on whether they are value or reference types.

    Now it starts to make sence why I don't feel very right here...

    Copy a question from thescripts.com, maybe a good question for your next interview:

    What's the difference among the following statements?

    int x = default(int);
    int x = 0;
    int x = new int();

  • 相关阅读:
    Frameset 框架
    FHS 文件层次标准
    history 命令
    QT基础走起
    Android中导入jar包v4的错误
    Android工具Eclipse点击卡死或者无响应情况
    让程序飞起来
    Android中报错
    【2019.9.23】NOIP2017 practice exam
    【技巧】时间复杂度
  • 原文地址:https://www.cnblogs.com/Hal/p/850114.html
Copyright © 2011-2022 走看看