Re: documenting exceptions
From: Steven T. Hatton (susudata_at_setidava.kushan.aa)
Date: 05/26/04
- Next message: Karl Heinz Buchegger: "Re: what does default operator= do?"
- Previous message: GGG: "shifting bits, shift 32 bits on 32 bit int"
- In reply to: Ian Lazarus: "documenting exceptions"
- Next in thread: Ian Lazarus: "Re: documenting exceptions"
- Reply: Ian Lazarus: "Re: documenting exceptions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 26 May 2004 14:33:16 -0400
Ian Lazarus wrote:
> Hello,
> Are you aware of any tool which analyzes source code and documents the
> exceptions thrown for each routine in each source file for a project?
> Thanks
This is one of the main reasons I don't like C++ exception syntax. I
understand there are legacy issues, but the fact that exceptions
potentially thrown by a function are not required to be part of the
signature bothers me. I believe the tool you are looking for is called a
good programmer.
-- STH Hatton's Law: "There is only One inviolable Law" KDevelop: http://www.kdevelop.org SuSE: http://www.suse.com Mozilla: http://www.mozilla.org
- Next message: Karl Heinz Buchegger: "Re: what does default operator= do?"
- Previous message: GGG: "shifting bits, shift 32 bits on 32 bit int"
- In reply to: Ian Lazarus: "documenting exceptions"
- Next in thread: Ian Lazarus: "Re: documenting exceptions"
- Reply: Ian Lazarus: "Re: documenting exceptions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|