zoukankan      html  css  js  c++  java
  • static vs const in c#

    All constants declarations are implicitly static, and the C# specification states that the (redundant) inclusion of the static modifier is prohibited. I believe this is to avoid the confusion which could occur if a reader were to see two constants, one declared static and one not - they could easily assume that the difference in specification implied a difference in semantics. Having said that, there is no prohibition on redundantly specifying an access modifier which is also the default one, where there is a choice. For instance, a (concrete) method can be explicitly marked as private despite that being the default. The rule appears to be that where there is no choice (e.g. a method declaration in an interface) the redundant modifier is prohibited. Where there is a choice, it's allowed.

     

    I think "const" and "static readonly" are not the same. The "const" must be known at compile time. However "static readonly" is initialized at runtime, but its the value cannot be changed (because it's readonly) after initialization.

    In practice, have a look at this example:

    // Trying to assign an instance of a class StorageFolder (which can't be known at compile time) to FOO

    // this will compile

    private static readonly StorageFolder   FOO = KnownFolders.DocumentsLibrary;

    // this won't compile

    private const  StorageFolder            FOO = KnownFolders.DocumentsLibrary;

  • 相关阅读:
    ssh登录很慢的问题
    Y480&Y580 刷slic2.1全自动教程
    re正则表达式5_*
    linux下查看内存使用情况
    检查linux网络的状况
    Linux Load average负载详细解释
    查看Linux磁盘空间大小
    Linux 批量重命名文件
    Linux 网卡丢包严重
    linux 下vi /vim 中文汉字乱码解决
  • 原文地址:https://www.cnblogs.com/jjj250/p/2848819.html
Copyright © 2011-2022 走看看