109 lines
3.7 KiB
HTML
109 lines
3.7 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
|
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
|
|
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
|
|
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 19.">
|
|
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
|
|
<TITLE>libstdc++-v3 HOWTO: Chapter 19</TITLE>
|
|
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/19_diagnostics/">
|
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
|
<!-- $Id: howto.html,v 1.3 2000/07/11 21:45:07 pme Exp $ -->
|
|
</HEAD>
|
|
<BODY>
|
|
|
|
<H1 CLASS="centered"><A NAME="top">Chapter 19: Diagnostics</A></H1>
|
|
|
|
<P>Chapter 19 deals with program diagnostics, such as exceptions
|
|
and assertions. You know, all the things we wish weren't even
|
|
necessary at all.
|
|
</P>
|
|
|
|
|
|
<!-- ####################################################### -->
|
|
<HR>
|
|
<H1>Contents</H1>
|
|
<UL>
|
|
<LI><A HREF="#1">Adding data to exceptions</A>
|
|
<LI><A HREF="#2">Exception class hierarchy diagram</A>
|
|
<LI><A HREF="#3">Concept checkers</A>
|
|
</UL>
|
|
|
|
<HR>
|
|
|
|
<!-- ####################################################### -->
|
|
|
|
<H2><A NAME="1">Adding data to exceptions</A></H2>
|
|
<P>The standard exception classes carry with them a single string as
|
|
data (usually describing what went wrong or where the 'throw' took
|
|
place). It's good to remember that you can add your own data to
|
|
these exceptions when extending the heirarchy:
|
|
</P>
|
|
<PRE>
|
|
using std::runtime_error;
|
|
struct My_Exception : public runtime_error
|
|
{
|
|
public:
|
|
My_Exception (const string& whatarg)
|
|
: runtime_error(whatarg), e(errno), id(GetDataBaseID()) { }
|
|
int errno_at_time_of_throw() const { return e; }
|
|
DBID id_of_thing_that_threw() const { return id; }
|
|
protected:
|
|
int e;
|
|
DBID id; // some user-defined type
|
|
};
|
|
</PRE>
|
|
<P>Return <A HREF="#top">to top of page</A> or
|
|
<A HREF="../faq/index.html">to the FAQ</A>.
|
|
</P>
|
|
|
|
<HR>
|
|
<H2><A NAME="2">Exception class hierarchy diagram</A></H2>
|
|
<P>The <A HREF="exceptions_hiearchy.pdf">diagram</A> is in PDF, or
|
|
at least it will be once it gets finished.
|
|
</P>
|
|
<P>Return <A HREF="#top">to top of page</A> or
|
|
<A HREF="../faq/index.html">to the FAQ</A>.
|
|
</P>
|
|
|
|
<HR>
|
|
<H2><A NAME="3">Concept checkers</A></H2>
|
|
<P>As part of their 3.3 release, SGI added some nifty macros which
|
|
perform assertions on type properties. For example, the Standard
|
|
requires that types passed as template parameters to <TT>vector</TT>
|
|
be "Assignable" (which means what you think it means).
|
|
</P>
|
|
<P>The concept checkers allow the source code for <TT>vector</TT> to
|
|
declare
|
|
<PRE>
|
|
__STL_CLASS_REQUIRES(_Tp, _Assignable);
|
|
</PRE>inside the template. <TT>_Tp</TT> is the element type of the
|
|
vector, and <TT>_Assignable</TT> is the concept to be checked (it is
|
|
defined in some back-end header files). When you instantiate
|
|
<TT>vector<MyType></TT>, compile-time checking can be done on
|
|
whether MyType meets the requirements for vectors.
|
|
</P>
|
|
<P>This is an extension to the library. This documentation needs updating.</P>
|
|
<P>Return <A HREF="#top">to top of page</A> or
|
|
<A HREF="../faq/index.html">to the FAQ</A>.
|
|
</P>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ####################################################### -->
|
|
|
|
<HR>
|
|
<P CLASS="fineprint"><EM>
|
|
Comments and suggestions are welcome, and may be sent to
|
|
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
|
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
|
<BR> $Id: howto.html,v 1.3 2000/07/11 21:45:07 pme Exp $
|
|
</EM></P>
|
|
|
|
|
|
</BODY>
|
|
</HTML>
|