From firstname.lastname@example.org Sat May 27 11:55:59 2000
Received: from localhost (localhost [127.0.0.1])
by www10.software.ibm.com (8.9.3/8.9.3) with ESMTP id LAA10730
for <email@example.com>; Sat, 27 May 2000 11:55:59 -0400
Date: Sat, 27 May 2000 11:55:59 -0400
Subject: warnings instead of errors
OS: Linux, NT4
Submission from: (NULL) (220.127.116.11)
Sometimes when I develop Java software I decide to comment out some lines of
code for testing purposes. But when these lines can throw an Exception there
is a try block around them that catches this Exception or the method containing
lines has a throws clause in its declaration.
Then the jikes compiler says that the catch block will never be reached because
Exception will never be thrown or something like this.
Sometimes I insert a return statement in the middle of a method because I dont
want the rest of it to be executed (debugging reasons again).
Then the compiler complains about unreachable code.
The problem is that the compiler handles these situation as fatal errors and
compiling my program.
I would appreciate it if the compiler would print a warning in such a situation
would continue compiling.
Take a look at gcc: This C compiler has compiler flags that tell him in which
situations it shall print warnings and if it shall stop then or not.
Sun Oct 8 01:48:57 2000 cabbey moved from incoming to suggestion