<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    gembin

    OSGi, Eclipse Equinox, ECF, Virgo, Gemini, Apache Felix, Karaf, Aires, Camel, Eclipse RCP

    HBase, Hadoop, ZooKeeper, Cassandra

    Flex4, AS3, Swiz framework, GraniteDS, BlazeDS etc.

    There is nothing that software can't fix. Unfortunately, there is also nothing that software can't completely fuck up. That gap is called talent.

    About Me

     

    Why int can't be passed to wrapper type Byte constructor?

    Let's take a look at the following code:

    class Program {
    public static void main (String[] args) {
    byte a = 1;
    Byte b = new Byte(primitiveByte);
    Byte c = new Byte(1);
    Byte d = new Byte((byte)1);
    System.out.print(b.byteValue() + c.byteValue());
    }
    }

    Why does the line "byte a = 1;" compile without error? and Why does the "Byte c = new Byte(1);" has a compile-time error?. Both of them use the integer literal value 1 within the range of byte. So why explicit casting "(byte)1" is needed?

    The assignment conversion (such as "byte a = 1;") is different than the method invocation conversion (such as "Byte c = new Byte(1);").  They are two subsections in Java Language Specification 3rd Edition:

    • 5.2 Assignment Conversion : Assignment conversion converts the type of an expression to the type of a specified variable.
    • 5.3 Method Invocation Conversion : Method invocation conversion is applied to each argument in a method or constructor invocation and, except in one case, performs the same conversions that assignment conversion does.

    Assignment Conversion

    Please read the above link for the detail about Assignment Conversion in Java. For our example:

    byte a = 1; 

    The assignment will not generate the compiler error because at any time if an integral value is assigned to any of the primitive types (byte, char, short), and the right hand side value is within the range of the left hand side data type, it will not generate an error. Hence as 1 is within the range of byte (-128 to 127), it is not generating compiler error. For example:

    byte a = 129; //Compile-time error

    When you assign an intergal value to any primitive type variable, the compiler will do a range checking to see if this value is in the range of the left side data type. If it is NOT within the range of data type, a compile-time error occurs.

    If the righ-hand of assignment is a variable or expression, can narrowing primitive conversions still work (5.1.3 Narrowing Primitive Conversions in Java Language Specification 3rd Edition)?

    • If the variable is a compile-time constant and the constants value is within the range of the left side data type, then it can be assigned to a narrower primitive type. Otherwise, a compiler error will occurs.
    • If the expression is a compile-time constant expression and the evaluated value is within the range of the left side data type, then it can be assigned to a narrower primitive type. Otherwise, a compiler time error will occurs.

    For example:

    int i1=1;
    final int i2 = 127;
    final int i3 = 245;
    byte b1 = i1; //Compile-time error, not final variable
    byte b2 = i2; //OK, compile time constant
    byte b3 = i3; //Compile-time error, over range
    byte b4 = (i2 + 2); //OK, compile time constant expression
    byte b5 = (i1 + 2); //Compile-time error, not final variable

    Method Invocation Conversion

    Please read the above link for the detail about the Method Invocation Conversion in Java. For our example:

    Byte c = new Byte(1);

    A compile-time error will occurs because you are passing an integer to the constructor of the Wrapper class Byte, the compiler will not do the implicit casting here.

    The method invocation conversions specifically do not include the implicit narrowing of integer constants which is part of assignment conversion. The designers of the Java programming language felt that including these implicit narrowing conversions would add additional complexity to the overloaded method matching resolution process.

    posted on 2010-07-08 15:11 gembin 閱讀(440) 評論(0)  編輯  收藏 所屬分類: JavaSE

    導(dǎo)航

    統(tǒng)計(jì)

    常用鏈接

    留言簿(6)

    隨筆分類(440)

    隨筆檔案(378)

    文章檔案(6)

    新聞檔案(1)

    相冊

    收藏夾(9)

    Adobe

    Android

    AS3

    Blog-Links

    Build

    Design Pattern

    Eclipse

    Favorite Links

    Flickr

    Game Dev

    HBase

    Identity Management

    IT resources

    JEE

    Language

    OpenID

    OSGi

    SOA

    Version Control

    最新隨筆

    搜索

    積分與排名

    最新評論

    閱讀排行榜

    評論排行榜

    free counters
    主站蜘蛛池模板: 国产免费福利体检区久久| 亚洲av永久无码精品秋霞电影秋| 免费一级特黄特色大片| 日本免费人成黄页在线观看视频| 亚洲日本乱码卡2卡3卡新区| 国产一精品一AV一免费孕妇| 色偷偷亚洲女人天堂观看欧| 久久精品免费一区二区喷潮| 一本天堂ⅴ无码亚洲道久久| 日本成人免费在线| 成人福利在线观看免费视频| 亚洲性在线看高清h片| 你懂的网址免费国产| 久久亚洲伊人中字综合精品| 最近中文字幕完整免费视频ww| 国产在线观看xxxx免费| 亚洲精品一品区二品区三品区| 国产精品99久久免费观看| 国产在线19禁免费观看国产 | 免费h黄肉动漫在线观看| 久久亚洲私人国产精品| 亚洲国产精品免费在线观看| 国产成人精品日本亚洲网址| 永久免费看mv网站入口| www在线观看免费视频| 亚洲ⅴ国产v天堂a无码二区| 国产1024精品视频专区免费| 日韩久久无码免费毛片软件| 国产成人精品日本亚洲| 五月婷婷综合免费| 日韩亚洲翔田千里在线| 亚洲国产成人一区二区精品区| 亚洲网站免费观看| 亚洲色图在线播放| 免费黄色app网站| 黄色视频在线免费观看| 亚洲免费网站在线观看| 99re6免费视频| 国产精品观看在线亚洲人成网| 亚洲色成人中文字幕网站| 国产曰批免费视频播放免费s|