Re: need argument for try catch blocks

From	"MikeP" <mp011011@some.org>
Newsgroups	comp.lang.c++
Subject	Re: need argument for try catch blocks
Date	2011-06-09 07:19 -0500
Organization	A noiseless patient Spider
Message-ID	<isqdod$ejp$1@dont-email.me> (permalink)
References	(9 earlier) <b03008e2-f261-4c7c-b2a9-71166c094f51@r35g2000prj.googlegroups.com> <ismbb6$doq$1@dont-email.me> <error-20110608043608@ram.dialup.fu-berlin.de> <isnomo$dev$1@dont-email.me> <isnov1$f37$1@dont-email.me>

Show all headers | View raw

MikeP wrote:
> MikeP wrote:
>> Stefan Ram wrote:
>>> "MikeP" <mp011011@some.org> writes:
>>>> describe an "error" scenario. Well then, that  would be a very much
>>>
>>>  What is an error?
>>>
>>>  So far, no one has given a general answer.
>>
>> Yes I have:
>>
>>> No, what you are describing above is a  "failure": a deviation from
>>> specifications. "error" precedes that and that is when there is
>>> still time to do something about the error. An error is the part of
>>> the system state that may likely lead to failure. An error is the
>>> thing you notice (detect) that is awry.
>>
>> Save for the choice of the word 'awry', I think that's right on
>> target (and that is in an ancillary sentence anyway). Extracting the
>> meat from the above gives:
>>
>>    An error is the part of the system state that may likely lead to
>> failure.
>
> "may likely" should probably be replaced with "can possibly". Picking
> nits now.

An error is the part of the system state with the potential to lead to 
failure.

("failure" probably needs a modifier.. I hesitate to put "system" in 
front of it as of yet though).

Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-06 05:22 -0500
  Re: need argument for try catch blocks Öö Tiib <ootiib@hot.ee> - 2011-06-06 21:53 -0700
    Re: need argument for try catch blocks Öö Tiib <ootiib@hot.ee> - 2011-06-06 23:48 -0700
      Re: need argument for try catch blocks Öö Tiib <ootiib@hot.ee> - 2011-06-07 00:18 -0700
    Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-07 07:13 -0500
      Re: need argument for try catch blocks Öö Tiib <ootiib@hot.ee> - 2011-06-07 07:33 -0700
        Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-07 10:08 -0500
          Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-07 10:12 -0500
            Re: need argument for try catch blocks Öö Tiib <ootiib@hot.ee> - 2011-06-07 13:59 -0700
              Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-07 16:48 -0500
                Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-07 18:20 -0500
          Re: need argument for try catch blocks Joshua Maurice <joshuamaurice@gmail.com> - 2011-06-07 14:42 -0700
            Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-07 18:13 -0500
              Re: need argument for try catch blocks Joshua Maurice <joshuamaurice@gmail.com> - 2011-06-07 16:21 -0700
                Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-07 19:13 -0500
              Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-08 07:07 -0500
                Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-08 07:12 -0500
                Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-09 07:19 -0500
                Re: need argument for try catch blocks "io_x" <a@b.c.invalid> - 2011-06-09 21:00 +0200
                Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-08 15:40 -0500
                Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-08 16:07 -0500
                Re: need argument for try catch blocks "MikeP" <mp011011@some.org> - 2011-06-09 10:21 -0500

csiph-web