Exception vs Boolean

C

Cor Ligthert [MVP]

Inline

Jon Skeet said:
Again, I don't think there's any real loss of context here. Which part
of which sentence do you think would have made the difference? I do
wish you'd stop accusing me of misquoting without being specific. It's
very tiresome.
I thought I cleared that in the rest of my previous message. To clarify that
even more confirm my ideas about that.

There have been in history and sadly still is done lots of situations where
(especially) the christian bible but I thought as well the koran are
misquoted by people, that has/does given many killings. Something that in my
opinion is completely in disharmony with the ideas of the main persons who
are quoted.

It are not only the words that are written but the intention from the
original quoted person that should count. But probably we disagree about
that as well.
The interesting thing is the negative attitude towards exceptions
expressed here though - it's all about trying to avoid them rather than
trying to use them where suitable. If you read the article, it's a lot
more positive in the impression it gives about exceptions.
I have expressely added my reply to the first reply from you where there was
not spoken about the article and not to that other thread. Thereby avoiding
that discussion. The first answer from Scott was a very clear text for me.
If you want to say that he did not wanted to say that, than I think that you
should not say that but Scott. This kind of talking for others I call
misquoting, because these messages stay and stand alone they give an opinion
as if Scott said that, while it was in my opinion you. If Scott says that
his first text was not meant as written, he is as far as I have seen his
message very good able to correct that.
Okay, but I *suspect* that's not what he meant either - given that he
mostly agrees with the article, I *suspect* he doesn't actually
recommend using an enum as an error code instead of using an exception.
If he *does* recommend that, then that's disagreeing with the article
again.
See my previous inline answer in this message.
(I still completely disagree with you on the idea that enums are more
descriptive than exceptions. The amount of information an enum can give
you is very limiting - exceptions can give as much information as they
want to. That's entirely my opinion, however, and nothing to do with
what Scott has written.)
This is in my opinion an exact answer that I did not wished to give in this
message thread. Accoording to my way of thinking. If you are not able to use
a boolean or a simple Enum, than you certainly should start thinking about
an exception. I did not write this because it was in my idea obvious in the
context of the other text I had written and still in the style of Scotts
first message.
 
C

Cor Ligthert [MVP]

Typo
I have seen his message = I have seen his messages (in past)

Cor Ligthert said:
Inline

Jon Skeet said:
Again, I don't think there's any real loss of context here. Which part
of which sentence do you think would have made the difference? I do
wish you'd stop accusing me of misquoting without being specific. It's
very tiresome.
I thought I cleared that in the rest of my previous message. To clarify
that even more confirm my ideas about that.

There have been in history and sadly still is done lots of situations
where (especially) the christian bible but I thought as well the koran are
misquoted by people, that has/does given many killings. Something that in
my opinion is completely in disharmony with the ideas of the main persons
who are quoted.

It are not only the words that are written but the intention from the
original quoted person that should count. But probably we disagree about
that as well.
The interesting thing is the negative attitude towards exceptions
expressed here though - it's all about trying to avoid them rather than
trying to use them where suitable. If you read the article, it's a lot
more positive in the impression it gives about exceptions.
I have expressely added my reply to the first reply from you where there
was not spoken about the article and not to that other thread. Thereby
avoiding that discussion. The first answer from Scott was a very clear
text for me. If you want to say that he did not wanted to say that, than I
think that you should not say that but Scott. This kind of talking for
others I call misquoting, because these messages stay and stand alone they
give an opinion as if Scott said that, while it was in my opinion you. If
Scott says that his first text was not meant as written, he is as far as I
have seen his message very good able to correct that.
Okay, but I *suspect* that's not what he meant either - given that he
mostly agrees with the article, I *suspect* he doesn't actually
recommend using an enum as an error code instead of using an exception.
If he *does* recommend that, then that's disagreeing with the article
again.
See my previous inline answer in this message.
(I still completely disagree with you on the idea that enums are more
descriptive than exceptions. The amount of information an enum can give
you is very limiting - exceptions can give as much information as they
want to. That's entirely my opinion, however, and nothing to do with
what Scott has written.)
This is in my opinion an exact answer that I did not wished to give in
this message thread. Accoording to my way of thinking. If you are not able
to use a boolean or a simple Enum, than you certainly should start
thinking about an exception. I did not write this because it was in my
idea obvious in the context of the other text I had written and still in
the style of Scotts first message.
 
C

Cor Ligthert [MVP]

Jon,

No problem, does not give any hard feeling from me.
Rome is as well not build in one day.

:)

Cor
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top