I had this when there was legacy code that we imported into Eclipse where
people had used semicolons to close { } blocks. Here's an example that would
cause an unreachable code:
try {
...
} catch (...) {...};
The semicolon is superfluous, but doesn't cause a problem in this block:
if(){...};
because it is interpreted as a complete Java statement which does nothing.
Same in the first example, except you can never get there. VisualAge doesn't
complain, but Eclipse does.
-Robert Douglass
-----Original Message-----
From: Leszek Gawron [mailto:[EMAIL PROTECTED]
Sent: Thursday, 06 March, 2003 9:32 PM
To: [EMAIL PROTECTED]
Subject: cocoon and new eclipse java compiler
I have updated my cocoon installation today and I started to get a LOOOT of
"Unreachable code" errors disappeared while switching back to Pizza
What may be a problem ?
ouzo
--
__
| / \ | Leszek Gawron // \\
\_\\ //_/ [EMAIL PROTECTED] _\\()//_
.'/()\'. Phone: +48(600)341118 / // \\ \
\\ // recursive: adj; see recursive | \__/ |
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
