Hello,
Let me to say what I think on that topic.
Guys If you don't know how to handle exception for a given method then
you are better off simply throwing it. Just add it to the method
declaration. That's all about that.
Handle only exceptions in case you are know for sure how to deal with
a
Yep. That's my approach.
Guys If you don't know how to handle exception for a given method then
you are better off simply throwing it.
This sentence may confuse some who will assume they have to catch it
in the first place. Maybe a better phrase is:
If you don't know how to handle exception
I still kind-of like listening to Joel and Jeff. Both make me cringe at
times, but I like their attitude towards product design and I think Joel
has quite some insight into the marketing/business side of software.
But I don't think I'd want either as the chief architect of some
enterprise
Number one clearly does not apply to checked exceptions, number two
applies to returning values, too. Of course you could assign a value and
follow the approach of having a single return statement at the end, but
I never understood why the resulting code should be any easier.
Peter
Martin
As I said: in cases where you want to have a version of your code where
the exception bubbles up and one where it doesn't you'll get the
duplication. I think that is usually a bad idea, although I must admit
the wrapper case you describe is an exception since the layer is the
same. I don't
I've had a bug reported by somebody using an older version of JRockit. I
was wondering if anybody knows where you can download them from? I can't
see any references on the JRockit download page…
http://www.oracle.com/technology/software/products/jrockit/index.html
Given that I had to use
Does
anyone
know
why
all
text
is
wrapped
at
column
70
?
It's
so
annoying...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups The
Java Posse group.
To post to this group, send email to javaposse@googlegroups.com
To
cos it email compatible. for those who subscribe.
On Aug 21, 8:11 pm, John Muir jm...@guskoeln.de wrote:
Does
anyone
know
why
all
text
is
wrapped
at
column
70
?
It's
so
annoying...
--~--~-~--~~~---~--~~
You received this message because you are
On Aug 21, 11:33 am, Peter Becker peter.becker...@gmail.com wrote:
Number one clearly does not apply to checked exceptions, number two
applies to returning values, too. Of course you could assign a value and
follow the approach of having a single return statement at the end, but
I never
I can follow your argument to some extent, but wouldn't the equivalent,
exception-based code have a try/catch block per if(goAhead)? I agree
that this would create code that is more verbose, but otherwise it seems
equivalent.
I take the point that it is possible to make code harder to read
I take the point that it is possible to make code harder to read using
exceptions in a way that is not possible without. I must admit I didn't
really think it through when I read Joel's blog post.
Joel seems to think of exceptions as mere alternative return points
and in that goto light, he
On 21 Aug., 15:50, Martin Wildam mwil...@gmail.com wrote:
I think the problem of context you also have when dealing with an
exception on the low level. Context is known most likely only by some
parent caller but on the other hand the parent caller often does not
have any clue about how some
On Aug 21, 2:07 pm, Peter Becker peter.becker...@gmail.com wrote:
I take the point that it is possible to make code harder to read using
exceptions in a way that is not possible without. I must admit I didn't
really think it through when I read Joel's blog post.
I think the reduced
Hi Possefolks,
I've been following both of the Exception-handling mega-threads and
have some opinions too, though unlikely original given the length of
the thread.
Checked exceptions *are* a failed experiment.
I thought they were a good idea when I first ran into them, but the
reality is quite
Does Spring Source have a professional service organization? i.e.
consultants? Even if they don't, maybe VMWare is looking to expand in
that direction by starting with Spring's existing development staff.
On Aug 10, 6:38 pm, Josh Long starbux...@gmail.com wrote:
VMWare buys SpringSource -
Martin Wildam wrote:
On Aug 21, 2:07 pm, Peter Becker peter.becker...@gmail.com wrote:
I take the point that it is possible to make code harder to read using
exceptions in a way that is not possible without. I must admit I didn't
really think it through when I read Joel's blog post.
B Smith-Mannschott wrote:
[...]
Some have argued that there's nothing wrong with checked exceptions,
per se, it's just that people don't use them right. This is akin to
acknowledging that every attempt to practice communism on a national
level has lead to a repressive police state, and yet
17 matches
Mail list logo
