On czw, mar 06, 2003 at 09:44:17 +0100, Robert Douglass wrote:
> 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.
nice but my problem is in xsp containing esql and very little xsp:logic
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]
