Re: unexpected exception handler

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EFDBBBF5-2152-4B57-A1F8-2173E66DE027@xxxxxxxxxxxxxxxx
Good point, Ben!


For the file stream I/O related (file stream read, write, seek, etc.), in
STL, are there any general base exception class which we could catch to
make
code at least could be notified such errors?

Exceptions outside software control are all OS exceptions, you can set up
handlers using __try/__catch/__finally SEH keywords or you can use the
set_se_translator function to convert these into a C++ exception type of
your choosing.



regards,
George

"Ben Voigt [C++ MVP]" wrote:

You sound as if exceptions just happen unpredictably, like earthquakes
or
tornadoes. Computers are deterministic state machines. Exceptions don't
occur at random, they are thrown by some piece of code in your
application. You are basically saying that you have no idea what your

That's not accurate. Computers have a lot of non-determinism. Some,
like
timing of hardware I/O, the software should expect and process without
exceptions. Others, like network or disk checksum failures, the software
should expect and may generate exceptions for internal flow control. But
yet others, like memory bit errors, could occur asynchronously and are
reported by a exception generated by hardware, randomly and from the
level
of abstraction of application software, perfectly so.

code is doing. That's not a good way to develop software.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925






.

Relevant Pages

  • Re: unexpected exception handler
    ... For the file stream I/O related (file stream read, write, seek, ... Exceptions outside software control are all OS exceptions, ... Under what circumstances would Windows report I/O error as a structured ... But see the comments to this blog entry for circumstances where I/O errors ...
    (microsoft.public.vc.language)
  • Re: unexpected exception handler
    ... Computers are deterministic state ... Exceptions don't occur at random, ... Computers have a lot of non-determinism. ... I consider the outcome of hardware I/O as input to the state machine, ...
    (microsoft.public.vc.language)
  • Re: unexpected exception handler
    ... I think for I/O fail, even if H/W fail, it should be reflected into some ... it should be possible to write code to catch all I/O exceptions -- there ... timing of hardware I/O, the software should expect and process without ...
    (microsoft.public.vc.language)
  • Re: unexpected exception handler
    ... Computers are deterministic state machines. ... Exceptions don't ... You are basically saying that you have no idea what your ... timing of hardware I/O, the software should expect and process without ...
    (microsoft.public.vc.language)