Skip to main content

Why label statement causes compile time error?

The following code has compile time error and why?
 
public class Program {
  public static void main(String[] args) {
    int counter = 0;
    label1:
      for (int i=0; i!=10; i++) {

        label2:
          int j = 0; //compile time error

          while (j++ < 10) {
            if (j > i) break label2; 
            if (j == i) {
              counter++;
              continue label1;
            }
          }
      }
    System.out.println(counter);
  }
}
From JLS:
Unlike C and C++, the Java programming language has no goto statement; identifier statement labels are used with break (?14.15) or continue (?14.16) statements appearing anywhere within the labeled statement.

The use of labels in loops and breaks has the following rules:
  • Any statement can have a label.
  • If a break statement has a label it must be the label of an enclosing statement.
  • If a continue statement has a label it must be the label of an enclosing loop.
In the above example, there are two problems. The first one is that label2 can't be followed immediately by a declaration statement, this is a syntax error. If we add another statement before the int j =0; to fix the syntax error, so that:
public class Program {
  public static void main(String[] args) {
    int counter = 0;
    label1:
      for (int i=0; i!=10; i++) {

        label2:
          System.out.println(i);
          int j = 0; 

          while (j++ < 10) {
            if (j > i) break label2; //compile time error
            if (j == i) {
              counter++;
              continue label1;
            }
          }
      }
    System.out.println(counter);
  }
}
It unveils the second problem, label2 must be on the enclosing statement, otherwise the compiler thinks label2 is missing.
We can fix the compiler error by simple adding parentheses to the above code. A group of statements enclosed in parentheses {}- called a code block - acts as a single statement. This way, label2 is on the whole enclosing statement.
public class Program {
  public static void main(String[] args) {
    int counter = 0;
    label1:
      for (int i=0; i!=10; i++) {

        label2:
        { //
        //the code compiles with or without this line
          System.out.println(i);
          int j = 0;
          while (j++ < 10) {
            if (j > i) break label2;
            if (j == i) {
              counter++;
              continue label1;
            }
          }
        } //
      }
    System.out.println(counter);
  }
}
 

Comments

Popular posts from this blog

Asynchronous Vs. Synchronous Communications

Synchronous (One thread):   1 thread -> |<---A---->||<----B---------->||<------C----->| Synchronous (multi-threaded):   thread A -> |<---A---->| \ thread B ------------> ->|<----B---------->| \ thread C ----------------------------------> ->|<------C----->|

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...

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