Skip to main content

Why narrowing primitive conversions from primitive long requires explicit casting?

Converting a large primitive type to a smaller primitive type is called narrowing primitive conversion. There's a special case known as an assignment conversion that handles some conversion without explicit casting.
Let's take a look at the following code:
class Program {
  public static void main(String[] args) {
     final int iVar = 10;
     byte  bVar = iVar;
     fianl int iVar1 = 345;
     byte  bVar1 = iVar1; //Compile time error
  }
}
In this example, a variable of type byte is being assigned a value of a constant expression of type int. This implies a narrowing conversion. We know that the value of constant expression must be in the range of variable's type for the assignment conversion to happen. In our example, as long as the value of iVar is for -128 to 127, the narrowing conversion is used in the assignment conversion.
The following code does not compile, even with the value of constant expression is in the range of type byte:
class Program {
  public static void main(String[] args) {
     final long lVar = 10;
     byte bVar = lVar; //compile time error
  }
}
Why the assignment conversion doesn't work here? We have a constant expression and the value is representable for the type byte. Here is answer from JLS:

5.2 Assignment Conversion in Java Language Specification 3rd Edition:
In addition, if the expression is a constant expression of type byte, short, char or int:
  • A narrowing primitive conversion MAY BE used if the type of the variable is byte, short, or char, and the value of the constant expression is representable in the type of the variable.
  • A narrowing primitive conversion followed by a boxing conversion may be used if the type of the variable is :
    • Byte and the value of the constant expression is representable in the type byte.
    • Short and the value of the constant expression is representable in the type short.
    • Character and the value of the constant expression is representable in the type char.
In the above example, the expression is a constant expression of type long and it is not covered by the special case. Therefore, a explicit cast must be used.
class Program {
  public static void main(String[] args) {
     final long lVar = 10;
     byte bVar = (byte)lVar;  
  }
}

Comments

  1. You might want to look at the += , -= , *= etc operations. These have implicity down casting as well.
    e.g.

    byte b = 5;
    b *= 2;
    System.out.println(b);

    Note: 5 and 2 are int types here, down cast to byte.

    However, consider this.

    byte b = 5;
    b *= 5.5;
    System.out.println(b);

    This prints 27. ;) i.e. its the same as
    b = (byte) ((int) 5 * (double) 5.5);

    ReplyDelete

Post a Comment

Popular posts from this blog

Advantages & Disadvantages of Synchronous / Asynchronous Communications?

  Asynchronous Communication Advantages: Requests need not be targeted to specific server. Service need not be available when request is made. No blocking, so resources could be freed.  Could use connectionless protocol Disadvantages: Response times are unpredictable. Error handling usually more complex.  Usually requires connection-oriented protocol.  Harder to design apps Synchronous Communication Advantages: Easy to program Outcome is known immediately  Error recovery easier (usually)  Better real-time response (usually) Disadvantages: Service must be up and ready. Requestor blocks, held resources are “tied up”.  Usually requires connection-oriented protocol

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag

XML Binding with JAXB 2.0 - Tutorial

Java Architecture for XML Binding (JAXB) is an API/framework that binds XML schema to Java representations. Java objects may then subsequently be used to marshal or unmarshal XML documents. Marshalling an XML document means creating an XML document from Java objects. Unmarshalling means creating creating a Java representation of an XML document (or, in effect, the reverse of marshaling). You retrieve the element and attribute values of the XML document from the Java representation. The JAXB 2.0 specification is implemented in JWSDP 2.0. JAXB 2.0 has some new features, which facilitate the marshalling and unmarshalling of an XML document. JAXB 2.0 also allows you to map a Java object to an XML document or an XML Schema. Some of the new features in JAXB 2.0 include: Smaller runtime libraries are required for JAXB 2.0, which require lesser runtime memory. Significantly, fewer Java classes are generated from a schema, compared to JAXB 1.0. For each top-level complexType, 2.0 generates a v