From 90782a9fe62b82d1e8ea243f11398f965b426f3e Mon Sep 17 00:00:00 2001 From: Emil Dotchevski Date: Thu, 9 Apr 2009 06:30:08 +0000 Subject: [PATCH] documentation update [SVN r52285] --- doc/error_info.html | 2 +- doc/source/boost-exception.reno | 6136 +++++++++++++++---------------- 2 files changed, 3069 insertions(+), 3069 deletions(-) diff --git a/doc/error_info.html b/doc/error_info.html index b14482a..8e7811e 100644 --- a/doc/error_info.html +++ b/doc/error_info.html @@ -56,7 +56,7 @@ typedef boost::error_info<struct tag_errno,int&

It can also be passed to get_error_info (#include <boost/exception/get_error_info.hpp> first) to retrieve the tag_errno int from a boost::exception:

catch( boost::exception & x )
     {
-    if( boost::shared_ptr<int const> e=boost::get_error_info<errno_info>(x) )
+    if( int const * e=boost::get_error_info<errno_info>(x) )
         ....
     }
diff --git a/doc/source/boost-exception.reno b/doc/source/boost-exception.reno index 28ea1e8..cb23860 100644 --- a/doc/source/boost-exception.reno +++ b/doc/source/boost-exception.reno @@ -48,59 +48,6 @@ reno_context - - - - - - 3 - 612485E090D76B2CC43C1A296F813075BA165C2496082E78E939F10B3DA8E09A - 1770110914 - 587 - 1462 - 60F3F48B87487FA6E0D2CCC0750AF435CC92CEC80BBBF609AC71295031AADD0D - 3929437933 - 361 - 213 - CD1241D84950468704F3C3F04116B8DA5162A8BEA4364F10951232F49113C5DE - 1658463867 - 121 - 238 - - - - - - 0 - ../../../../boost/throw_exception.hpp - 0 - 0 - - - - - <string>configuration macros</string> - - - - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 6 - - reno_context - @@ -146,50 +93,7 @@ 0 - 7 - - reno_context - - - - - - - 1 - FC684D0DD5A9732B4130F2AB3DB6E0491D0F523E14B7FB738B2019EA2C7F8717 - 2229778754 - 631 - 319 - - - - - - 0 - ../../example/cloning_2.cpp - 0 - 0 - - - - - <string>cloning and re-throwing an exception</string> - - - cloning_and_rethrowing - - - - - - 0 - - - - - 0 - - 8 + 6 reno_context @@ -238,7 +142,7 @@ 0 - 9 + 7 reno_context @@ -247,29 +151,33 @@ - 2 - 1D3204D3ADDAB7AA716BEA1489EA852A9D6B5C110243364F6931FEF1CC2E5F88 - 422052608 - 3923 - 518 - 6E325144EF4F41FA3A225EB30729101382C4E99B3D6160E307311E4B4E641010 - 1097215175 - 161 - 240 + 3 + 612485E090D76B2CC43C1A296F813075BA165C2496082E78E939F10B3DA8E09A + 1770110914 + 587 + 1462 + 60F3F48B87487FA6E0D2CCC0750AF435CC92CEC80BBBF609AC71295031AADD0D + 3929437933 + 361 + 213 + CD1241D84950468704F3C3F04116B8DA5162A8BEA4364F10951232F49113C5DE + 1658463867 + 121 + 238 0 - ../../../../boost/exception/info.hpp + ../../../../boost/throw_exception.hpp 0 0 - <string>error_info::error_info</string> + <string>configuration macros</string> @@ -287,703 +195,7 @@ 0 - 10 - - reno_context - - - - - - - 2 - F7633FDCF6615C0199645701EE6E7ACE5CBCD7A7CF6838573791E91ABB3C09F2 - 1668435395 - 1332 - 396 - A1F443AF571973A12005D2F7D4AE09A32AAF686FEEAE272EC21512A65EB943E8 - 3879093659 - 1300 - 26 - - - - - - 0 - ../../../../boost/exception/info_tuple.hpp - 0 - 0 - - - - - <string>tuple/operator<<</string> - - - - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 11 - - reno_context - - - - - - - 0 - - - - - - 1 - - - - - <string>transporting of arbitrary data to the catch site</string> - - - tutorial_transporting_data - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 12 - - reno_context - - - - - - - 1 - 55F1164770FD778354E151EF65A3E830DA20F325F7ED20A95130A4B83FC801BF - 1282550303 - 9192 - 323 - - - - - - 0 - ../../../../boost/exception/exception.hpp - 0 - 0 - - - - - <string>boost/exception/exception.hpp</string> - - - exception_exception_hpp - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 13 - - reno_context - - - - - - - 2 - 9748FFBBC9F02FEB97E0BA1E6280C51FFF5D7F217F0F12EE8ED29F6BE5CCCE44 - 2533933282 - 8724 - 615 - 0066D4E6E6B189906E6DE04F08509F3737511701A1B1355B37511EC18E8371F4 - 2078296250 - 305 - 8156 - - - - - - 0 - ../../../../boost/exception_ptr.hpp - 0 - 0 - - - - - <string>copy_exception</string> - - - - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 14 - - reno_context - - - - - - - 1 - 7116AEECEA666794E31DC99390ADEC1BA6AF74B2398067A0739767B4B76FA97A - 4128134227 - 307 - 302 - - - - - - 0 - ../../example/logging.cpp - 0 - 0 - - - - - <string>diagnostic information</string> - - - tutorial_diagnostic_information - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 15 - - reno_context - - - - - - - 1 - 2F432507CFD796BE673F33D9AC68C535F1ED1F4FCD3A8E3AEEC320D9795FB4AE - 2319362875 - 2574 - 323 - - - - - - 0 - ../../../../boost/exception/get_error_info.hpp - 0 - 0 - - - - - <string>boost/exception/get_error_info.hpp</string> - - - exception_get_error_info_hpp - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 16 - - reno_context - - - - - - - 0 - - - - - - 1 - - - - - <string>frequently asked questions</string> - - - - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 17 - - reno_context - - - - - - - 2 - 1D3204D3ADDAB7AA716BEA1489EA852A9D6B5C110243364F6931FEF1CC2E5F88 - 422052608 - 3923 - 518 - D31BCE814DF5B8B718E7EB67A194AD08EF716A26D422E436596ABA1F145007D8 - 4055211476 - 525 - 3392 - - - - - - 0 - ../../../../boost/exception/info.hpp - 0 - 0 - - - - - <string>exception/operator<<</string> - - - - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 18 - - reno_context - - - - - - - 0 - - - - - - 1 - - - - - <string>Motivation</string> - - - motivation - - - - - - 7 - 2 - (:include include:) (:auto also explicit=" - 1 - - 0 - - 19 - - reno_context - - - - - - - 0 - - - - - - 1 - - - - - <string>exception types as simple semantic tags</string> - - - - - - - - 2 - - 1 - - 0 - - 20 - - reno_context - - - - - - - 1 - D9B8E6AA12A4F33953B1A961FA590C5A3840234B6531CA8C04AC985AD5800835 - 2432554768 - 702 - 408 - - - - - - 0 - ../../example/enable_error_info.cpp - 0 - 0 - - - - - <string>integrating boost exception in existing exception class hierarchies</string> - - - tutorial_enable_error_info - - - - - 2 - - 1 - - 0 - - -16 - - - 2 - ":) - - - - - 0 - - -19 - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - -20 - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 21 - - reno_context - - - - - - - 2 - 55F1164770FD778354E151EF65A3E830DA20F325F7ED20A95130A4B83FC801BF - 1282550303 - 9192 - 323 - F3FB15CD82336271C6E875BC620385322777D16F0B7C233300783CE35710CCBF - 3292878997 - 282 - 7305 - - - - - - 0 - ../../../../boost/exception/exception.hpp - 0 - 0 - - - - - <string>enable_error_info</string> - - - - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 22 - - reno_context - - - - - - - 2 - 9748FFBBC9F02FEB97E0BA1E6280C51FFF5D7F217F0F12EE8ED29F6BE5CCCE44 - 2533933282 - 8724 - 615 - F86EB07D04CD0D0645080D1121DA899746D0C45137E17E1D9BE605E75396F047 - 1983537541 - 1346 - 148 - - - - - - 0 - ../../../../boost/exception_ptr.hpp - 0 - 0 - - - - - <string>exception_ptr</string> - - - - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 23 - - reno_context - - - - - - - 2 - 55F1164770FD778354E151EF65A3E830DA20F325F7ED20A95130A4B83FC801BF - 1282550303 - 9192 - 323 - 17E691632123EB67BA67D590B49EB8094F462F5A10A66A1C5438E1867EF1478E - 765399792 - 77 - 5917 - - - - - - 0 - ../../../../boost/exception/exception.hpp - 0 - 0 - - - - - <string>exception::~exception</string> - - - exception_destructor - - - - - - 1 - 2 - (:include include:) (:auto also:) - - - - - 0 - - 24 - - reno_context - - - - - - - 1 - E444EE9697EEADFDE0767E1D0242FC0E70D98E61FB1F0FFA099648DE509B82F3 - 94503238 - 773 - 374 - - - - - - 0 - ../../example/info_tuple.cpp - 0 - 0 - - - - - <string>adding grouped data to exceptions</string> - - - grouping_data - - - - - - 0 - - - - - 0 - - 25 + 8 reno_context @@ -1028,6 +240,789 @@ (:include include:) (:auto also:) + + + 0 + + 9 + + reno_context + + + + + + + 1 + FC684D0DD5A9732B4130F2AB3DB6E0491D0F523E14B7FB738B2019EA2C7F8717 + 2229778754 + 631 + 319 + + + + + + 0 + ../../example/cloning_2.cpp + 0 + 0 + + + + + <string>cloning and re-throwing an exception</string> + + + cloning_and_rethrowing + + + + + + 0 + + + + + 0 + + 10 + + reno_context + + + + + + + 1 + 7116AEECEA666794E31DC99390ADEC1BA6AF74B2398067A0739767B4B76FA97A + 4128134227 + 307 + 302 + + + + + + 0 + ../../example/logging.cpp + 0 + 0 + + + + + <string>diagnostic information</string> + + + tutorial_diagnostic_information + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 11 + + reno_context + + + + + + + 2 + 1D3204D3ADDAB7AA716BEA1489EA852A9D6B5C110243364F6931FEF1CC2E5F88 + 422052608 + 3923 + 518 + 6E325144EF4F41FA3A225EB30729101382C4E99B3D6160E307311E4B4E641010 + 1097215175 + 161 + 240 + + + + + + 0 + ../../../../boost/exception/info.hpp + 0 + 0 + + + + + <string>error_info::error_info</string> + + + + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 12 + + reno_context + + + + + + + 2 + F7633FDCF6615C0199645701EE6E7ACE5CBCD7A7CF6838573791E91ABB3C09F2 + 1668435395 + 1332 + 396 + A1F443AF571973A12005D2F7D4AE09A32AAF686FEEAE272EC21512A65EB943E8 + 3879093659 + 1300 + 26 + + + + + + 0 + ../../../../boost/exception/info_tuple.hpp + 0 + 0 + + + + + <string>tuple/operator<<</string> + + + + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 13 + + reno_context + + + + + + + 0 + + + + + + 1 + + + + + <string>transporting of arbitrary data to the catch site</string> + + + tutorial_transporting_data + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 14 + + reno_context + + + + + + + 1 + 55F1164770FD778354E151EF65A3E830DA20F325F7ED20A95130A4B83FC801BF + 1282550303 + 9192 + 323 + + + + + + 0 + ../../../../boost/exception/exception.hpp + 0 + 0 + + + + + <string>boost/exception/exception.hpp</string> + + + exception_exception_hpp + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 15 + + reno_context + + + + + + + 2 + 9748FFBBC9F02FEB97E0BA1E6280C51FFF5D7F217F0F12EE8ED29F6BE5CCCE44 + 2533933282 + 8724 + 615 + 0066D4E6E6B189906E6DE04F08509F3737511701A1B1355B37511EC18E8371F4 + 2078296250 + 305 + 8156 + + + + + + 0 + ../../../../boost/exception_ptr.hpp + 0 + 0 + + + + + <string>copy_exception</string> + + + + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 16 + + reno_context + + + + + + + 1 + 2F432507CFD796BE673F33D9AC68C535F1ED1F4FCD3A8E3AEEC320D9795FB4AE + 2319362875 + 2574 + 323 + + + + + + 0 + ../../../../boost/exception/get_error_info.hpp + 0 + 0 + + + + + <string>boost/exception/get_error_info.hpp</string> + + + exception_get_error_info_hpp + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 17 + + reno_context + + + + + + + 0 + + + + + + 1 + + + + + <string>frequently asked questions</string> + + + + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 18 + + reno_context + + + + + + + 2 + 1D3204D3ADDAB7AA716BEA1489EA852A9D6B5C110243364F6931FEF1CC2E5F88 + 422052608 + 3923 + 518 + D31BCE814DF5B8B718E7EB67A194AD08EF716A26D422E436596ABA1F145007D8 + 4055211476 + 525 + 3392 + + + + + + 0 + ../../../../boost/exception/info.hpp + 0 + 0 + + + + + <string>exception/operator<<</string> + + + + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 19 + + reno_context + + + + + + + 0 + + + + + + 1 + + + + + <string>boost/exception/enable_current_exception.hpp</string> + + + exception_enable_current_exception_hpp + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 20 + + reno_context + + + + + + + 0 + + + + + + 1 + + + + + <string>Motivation</string> + + + motivation + + + + + + 7 + 2 + (:include include:) (:auto also explicit=" + 1 + + 0 + + 21 + + reno_context + + + + + + + 0 + + + + + + 1 + + + + + <string>exception types as simple semantic tags</string> + + + + + + + + 2 + + 1 + + 0 + + 22 + + reno_context + + + + + + + 1 + D9B8E6AA12A4F33953B1A961FA590C5A3840234B6531CA8C04AC985AD5800835 + 2432554768 + 702 + 408 + + + + + + 0 + ../../example/enable_error_info.cpp + 0 + 0 + + + + + <string>integrating boost exception in existing exception class hierarchies</string> + + + tutorial_enable_error_info + + + + + 2 + + 1 + + 0 + + -17 + + + 2 + ":) + + + + + 0 + + -21 + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + -22 + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 23 + + reno_context + + + + + + + 2 + 55F1164770FD778354E151EF65A3E830DA20F325F7ED20A95130A4B83FC801BF + 1282550303 + 9192 + 323 + F3FB15CD82336271C6E875BC620385322777D16F0B7C233300783CE35710CCBF + 3292878997 + 282 + 7305 + + + + + + 0 + ../../../../boost/exception/exception.hpp + 0 + 0 + + + + + <string>enable_error_info</string> + + + + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 24 + + reno_context + + + + + + + 2 + 9748FFBBC9F02FEB97E0BA1E6280C51FFF5D7F217F0F12EE8ED29F6BE5CCCE44 + 2533933282 + 8724 + 615 + F86EB07D04CD0D0645080D1121DA899746D0C45137E17E1D9BE605E75396F047 + 1983537541 + 1346 + 148 + + + + + + 0 + ../../../../boost/exception_ptr.hpp + 0 + 0 + + + + + <string>exception_ptr</string> + + + + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 25 + + reno_context + + + + + + + 2 + 55F1164770FD778354E151EF65A3E830DA20F325F7ED20A95130A4B83FC801BF + 1282550303 + 9192 + 323 + 17E691632123EB67BA67D590B49EB8094F462F5A10A66A1C5438E1867EF1478E + 765399792 + 77 + 5917 + + + + + + 0 + ../../../../boost/exception/exception.hpp + 0 + 0 + + + + + <string>exception::~exception</string> + + + exception_destructor + + + + + + 1 + 2 + (:include include:) (:auto also:) + + 0 @@ -1036,6 +1031,49 @@ reno_context + + + + + + 1 + E444EE9697EEADFDE0767E1D0242FC0E70D98E61FB1F0FFA099648DE509B82F3 + 94503238 + 773 + 374 + + + + + + 0 + ../../example/info_tuple.cpp + 0 + 0 + + + + + <string>adding grouped data to exceptions</string> + + + grouping_data + + + + + + 0 + + + + + 0 + + 27 + + reno_context + @@ -1073,44 +1111,6 @@ (:include include:) (:auto also:) - - - 0 - - 27 - - reno_context - - - - - - - 0 - - - - - - 1 - - - - - <string>boost/exception/enable_current_exception.hpp</string> - - - exception_enable_current_exception_hpp - - - - - - 1 - 2 - (:include include:) (:auto also:) - - 0 @@ -1168,6 +1168,44 @@ reno_context + + + + + + 0 + + + + + + 1 + + + + + <string>Synopsis</string> + + + synopsis + + + + + + 1 + 2 + (:include include:) (:auto also:) + + + + + 0 + + 30 + + reno_context + @@ -1207,7 +1245,7 @@ 0 - 30 + 31 reno_context @@ -1256,7 +1294,7 @@ 0 - 31 + 32 reno_context @@ -1309,7 +1347,7 @@ 0 - 32 + 33 reno_context @@ -1354,7 +1392,7 @@ 0 - 33 + 34 reno_context @@ -1397,7 +1435,7 @@ 0 - 34 + 35 reno_context @@ -1417,10 +1455,10 @@ - <string>Synopsis</string> + <string>Functions</string> - synopsis + functions @@ -1435,7 +1473,7 @@ 0 - 35 + 36 reno_context @@ -1484,7 +1522,7 @@ 0 - 36 + 37 reno_context @@ -1533,7 +1571,7 @@ 0 - 37 + 38 reno_context @@ -1571,7 +1609,7 @@ 0 - 38 + 39 reno_context @@ -1609,7 +1647,7 @@ 0 - 39 + 40 reno_context @@ -1658,7 +1696,7 @@ 0 - 40 + 41 reno_context @@ -1707,7 +1745,7 @@ 0 - 41 + 42 reno_context @@ -1745,7 +1783,7 @@ 0 - 42 + 43 reno_context @@ -1794,7 +1832,7 @@ 0 - 43 + 44 reno_context @@ -1843,7 +1881,7 @@ 0 - 44 + 45 reno_context @@ -1896,7 +1934,7 @@ 0 - 45 + 46 reno_context @@ -1939,7 +1977,7 @@ 0 - 46 + 47 reno_context @@ -1977,7 +2015,7 @@ 0 - 47 + 48 reno_context @@ -2016,44 +2054,6 @@ 0 - - - 0 - - 48 - - reno_context - - - - - - - 0 - - - - - - 1 - - - - - <string>Functions</string> - - - functions - - - - - - 1 - 2 - (:include include:) (:auto also:) - - 0 @@ -3007,36 +3007,7 @@ - 7 - 2 - [@class (:link - 1 - - 0 - - -42 - - - 2 - :) { protected: (:include - 1 - - 0 - - -44 - - - 2 - decl pre_indent="4":) (:include - 1 - - 0 - - -23 - - - 2 - decl pre_indent="4":) };@] + 0 @@ -3046,6 +3017,46 @@ -43 + + 7 + 2 + [@class (:link + 1 + + 0 + + -43 + + + 2 + :) { protected: (:include + 1 + + 0 + + -45 + + + 2 + decl pre_indent="4":) (:include + 1 + + 0 + + -25 + + + 2 + decl pre_indent="4":) };@] + + + + + 0 + + -44 + + 9 2 @@ -3054,7 +3065,7 @@ 0 - -43 + -44 2 @@ -3072,7 +3083,7 @@ 0 - -9 + -11 2 @@ -3081,24 +3092,13 @@ 0 - -31 + -32 2 decl pre_indent="4":) };@] - - - 0 - - -44 - - - - 0 - - 0 @@ -3374,54 +3374,7 @@ - 11 - 2 - [@(:include - 1 - - 0 - - -42 - - - 2 - def:) (:include - 1 - - 0 - - -43 - - - 2 - decl:) typedef (:link - 1 - - 0 - - -43 - - - 2 - :)<struct tag_throw_function,char const *> throw_function; typedef (:link - 1 - - 0 - - -43 - - - 2 - :)<struct tag_throw_file,char const *> throw_file; typedef (:link - 1 - - 0 - - -43 - - - 2 - :)<struct tag_throw_line,int> throw_line;@] + 0 @@ -3443,7 +3396,54 @@ - 0 + 11 + 2 + [@(:include + 1 + + 0 + + -43 + + + 2 + def:) (:include + 1 + + 0 + + -44 + + + 2 + decl:) typedef (:link + 1 + + 0 + + -44 + + + 2 + :)<struct tag_throw_function,char const *> throw_function; typedef (:link + 1 + + 0 + + -44 + + + 2 + :)<struct tag_throw_file,char const *> throw_file; typedef (:link + 1 + + 0 + + -44 + + + 2 + :)<struct tag_throw_line,int> throw_line;@] @@ -3454,18 +3454,7 @@ - 3 - 2 - [@(:include - 1 - - 0 - - -36 - - - 2 - decl:)@] + 0 @@ -3476,7 +3465,18 @@ - 0 + 3 + 2 + [@(:include + 1 + + 0 + + -37 + + + 2 + decl:)@] @@ -3509,7 +3509,18 @@ - 0 + 3 + 2 + [@(:include + 1 + + 0 + + -8 + + + 2 + decl:)@] @@ -3597,18 +3608,7 @@ - 3 - 2 - [@(:include - 1 - - 0 - - -25 - - - 2 - decl:)@] + 0 @@ -3662,6 +3662,17 @@ -32 + + 0 + + + + + 0 + + -33 + + 5 2 @@ -3670,7 +3681,7 @@ 0 - -6 + -5 2 @@ -3686,17 +3697,6 @@ decl:)@] - - - 0 - - -33 - - - - 0 - - 0 @@ -3877,7 +3877,7 @@ 0 - -10 + -12 2 @@ -3899,7 +3899,7 @@ 0 - -32 + -33 2 @@ -3917,7 +3917,7 @@ 0 - -12 + -14 2 @@ -3926,7 +3926,7 @@ 0 - -15 + -16 2 @@ -3986,7 +3986,7 @@ 0 - -21 + -23 2 @@ -4019,7 +4019,7 @@ 0 - -43 + -44 2 @@ -4052,7 +4052,7 @@ 0 - -43 + -44 2 @@ -4061,7 +4061,7 @@ 0 - -17 + -18 2 @@ -4083,7 +4083,7 @@ 0 - -35 + -36 2 @@ -4092,7 +4092,7 @@ 0 - -22 + -24 2 @@ -4101,7 +4101,7 @@ 0 - -13 + -15 2 @@ -4110,7 +4110,7 @@ 0 - -8 + -6 2 @@ -4119,7 +4119,7 @@ 0 - -40 + -41 2 @@ -4141,7 +4141,7 @@ 0 - -26 + -27 2 @@ -4150,7 +4150,7 @@ 0 - -39 + -40 2 @@ -4183,7 +4183,7 @@ 0 - -30 + -31 2 @@ -4212,7 +4212,18 @@ - 0 + 3 + 2 + [@template <class E> std::string (:link + 1 + + 0 + + -5 + + + 2 + :)( E const & e );@] @@ -4223,9 +4234,18 @@ - 3 + 5 2 - [@template <class E> std::string (:link + [@(:link + 1 + + 0 + + -24 + + + 2 + :) (:link 1 0 @@ -4234,7 +4254,7 @@ 2 - :)( E const & e );@] + :)();@] @@ -4256,18 +4276,9 @@ - 5 + 3 2 - [@(:link - 1 - - 0 - - -22 - - - 2 - :) (:link + [@template <class T> ---unspecified--- (:link 1 0 @@ -4276,7 +4287,7 @@ 2 - :)();@] + :)( T const & e );@] @@ -4286,6 +4297,28 @@ -9 + + 0 + + + + + 0 + + -10 + + + + 0 + + + + + 0 + + -11 + + 5 2 @@ -4294,7 +4327,7 @@ 0 - -9 + -11 2 @@ -4314,7 +4347,7 @@ 0 - -10 + -12 @@ -4325,7 +4358,7 @@ 0 - -10 + -12 2 @@ -4334,7 +4367,7 @@ 0 - -43 + -44 2 @@ -4343,35 +4376,13 @@ 0 - -43 + -44 2 :)<TagN,TN> > const & v );@] - - - 0 - - -11 - - - - 0 - - - - - 0 - - -12 - - - - 0 - - 0 @@ -4380,27 +4391,7 @@ - 5 - 2 - [@template <class T> (:link - 1 - - 0 - - -22 - - - 2 - :) (:link - 1 - - 0 - - -13 - - - 2 - :)( T const & e );@] + 0 @@ -4422,7 +4413,27 @@ - 0 + 5 + 2 + [@template <class T> (:link + 1 + + 0 + + -24 + + + 2 + :) (:link + 1 + + 0 + + -15 + + + 2 + :)( T const & e );@] @@ -4444,27 +4455,7 @@ - 5 - 2 - [@template <class E, class Tag, class T> E const & (:link - 1 - - 0 - - -17 - - - 2 - mod="/":)( E const & x, (:link - 1 - - 0 - - -43 - - - 2 - :)<Tag,T> const & v );@] + 0 @@ -4475,7 +4466,27 @@ - 0 + 5 + 2 + [@template <class E, class Tag, class T> E const & (:link + 1 + + 0 + + -18 + + + 2 + mod="/":)( E const & x, (:link + 1 + + 0 + + -44 + + + 2 + :)<Tag,T> const & v );@] @@ -4508,18 +4519,7 @@ - 3 - 2 - [@template <class T> ---unspecified--- (:link - 1 - - 0 - - -21 - - - 2 - :)( T const & x );@] + 0 @@ -4530,18 +4530,7 @@ - 3 - 2 - [@typedef ---unspecified--- (:link - 1 - - 0 - - -22 - - - 2 - :);@] + 0 @@ -4554,7 +4543,7 @@ 3 2 - [@(:link + [@template <class T> ---unspecified--- (:link 1 0 @@ -4563,7 +4552,7 @@ 2 - mod="m":)();@] + :)( T const & x );@] @@ -4574,7 +4563,18 @@ - 0 + 3 + 2 + [@typedef ---unspecified--- (:link + 1 + + 0 + + -24 + + + 2 + :);@] @@ -4587,7 +4587,7 @@ 3 2 - [@template <class T> ---unspecified--- (:link + [@(:link 1 0 @@ -4596,7 +4596,7 @@ 2 - :)( T const & e );@] + mod="m":)();@] @@ -4607,90 +4607,7 @@ - 19 - 2 - [@#if !defined( BOOST_EXCEPTION_DISABLE ) #include <(:link - 1 - - 0 - - -12 - - - 2 - :)> #include <boost/current_function.hpp> #define (:link - 1 - - 0 - - -26 - - - 2 - :)(x)\ ::boost::(:link - 1 - - 0 - - -39 - - - 2 - :)( ::boost::(:link - 1 - - 0 - - -21 - - - 2 - :)(x) <<\ ::boost::(:link - 1 - - 0 - - -12 - - - 2 - |throw_function:)(BOOST_CURRENT_FUNCTION) <<\ ::boost::(:link - 1 - - 0 - - -12 - - - 2 - |throw_file:)(__FILE__) <<\ ::boost::(:link - 1 - - 0 - - -12 - - - 2 - |throw_line:)((int)__LINE__) ) #else #define (:link - 1 - - 0 - - -26 - - - 2 - :)(x) ::boost::(:link - 1 - - 0 - - -39 - - - 2 - :)(x) #endif@] + 0 @@ -4701,7 +4618,90 @@ - 0 + 19 + 2 + [@#if !defined( BOOST_EXCEPTION_DISABLE ) #include <(:link + 1 + + 0 + + -14 + + + 2 + :)> #include <boost/current_function.hpp> #define (:link + 1 + + 0 + + -27 + + + 2 + :)(x)\ ::boost::(:link + 1 + + 0 + + -40 + + + 2 + :)( ::boost::(:link + 1 + + 0 + + -23 + + + 2 + :)(x) <<\ ::boost::(:link + 1 + + 0 + + -14 + + + 2 + |throw_function:)(BOOST_CURRENT_FUNCTION) <<\ ::boost::(:link + 1 + + 0 + + -14 + + + 2 + |throw_file:)(__FILE__) <<\ ::boost::(:link + 1 + + 0 + + -14 + + + 2 + |throw_line:)((int)__LINE__) ) #else #define (:link + 1 + + 0 + + -27 + + + 2 + :)(x) ::boost::(:link + 1 + + 0 + + -40 + + + 2 + :)(x) #endif@] @@ -4744,6 +4744,17 @@ -30 + + 0 + + + + + 0 + + -31 + + 3 2 @@ -4752,7 +4763,7 @@ 0 - -30 + -31 2 @@ -4763,7 +4774,7 @@ 0 - -31 + -32 @@ -4783,24 +4794,13 @@ 0 - -31 + -32 2 mod="m":)() const;@] - - - 0 - - -32 - - - - 0 - - 0 @@ -4830,6 +4830,17 @@ -35 + + 0 + + + + + 0 + + -36 + + 5 2 @@ -4838,7 +4849,7 @@ 0 - -35 + -36 2 @@ -4847,7 +4858,7 @@ 0 - -42 + -43 2 @@ -4858,7 +4869,7 @@ 0 - -36 + -37 @@ -4878,24 +4889,13 @@ 0 - -36 + -37 2 :)( E const & x );@] - - - 0 - - -37 - - - - 0 - - 0 @@ -4915,27 +4915,7 @@ - 5 - 2 - [@#ifdef BOOST_NO_EXCEPTIONS void (:link - 1 - - 0 - - -39 - - - 2 - :)( std::exception const & e ); // user defined #else template <class E> void (:link - 1 - - 0 - - -39 - - - 2 - :)( E const & e ); #endif@] + 0 @@ -4948,7 +4928,7 @@ 5 2 - [@void (:link + [@#ifdef BOOST_NO_EXCEPTIONS void (:link 1 0 @@ -4957,16 +4937,16 @@ 2 - :)( (:link + :)( std::exception const & e ); // user defined #else template <class E> void (:link 1 0 - -22 + -40 2 - :) const & ep ); + :)( E const & e ); #endif@] @@ -4977,7 +4957,27 @@ - 0 + 5 + 2 + [@void (:link + 1 + + 0 + + -41 + + + 2 + :)( (:link + 1 + + 0 + + -24 + + + 2 + :) const & ep ); @@ -4988,18 +4988,7 @@ - 3 - 2 - [@class (:link - 1 - - 0 - - -42 - - - 2 - :);@] + 0 @@ -5012,7 +5001,7 @@ 3 2 - [@template <class Tag,class T> class (:link + [@class (:link 1 0 @@ -5032,9 +5021,9 @@ - 7 + 3 2 - [@(:link + [@template <class Tag,class T> class (:link 1 0 @@ -5043,25 +5032,7 @@ 2 - mod="m":)(); (:link - 1 - - 0 - - -44 - - - 2 - mod="m":)( (:link - 1 - - 0 - - -42 - - - 2 - :) const & x );@] + :);@] @@ -5072,7 +5043,36 @@ - 0 + 7 + 2 + [@(:link + 1 + + 0 + + -45 + + + 2 + mod="m":)(); (:link + 1 + + 0 + + -45 + + + 2 + mod="m":)( (:link + 1 + + 0 + + -43 + + + 2 + :) const & x );@] @@ -5272,6 +5272,284 @@ -5 + + 29 + 2 + (:auto !!!:) (:include synopsis:) !!!!Returns: A string value that contains varying amount of implementation-specific diagnostic information about the passed exception object: *If E can be statically converted to boost::(:link + 1 + + 0 + + -43 + + + 2 + :), the returned value contains the string representations of all (:link + 1 + + 0 + + -44 + + + 2 + :) objects stored in the boost::(:link + 1 + + 0 + + -43 + + + 2 + :) through (:link + 1 + + 0 + + -18 + + + 2 + mod="/":), along with other diagnostic information relevant to the exception. If e can be dynamically converted to std::exception, the returned value also contains the what() string. *Otherwise, if E can be statically converted std::exception: **if e can be dynamically converted to boost::exception, the returned value is the same as if E could be statically converted to boost::(:link + 1 + + 0 + + -43 + + + 2 + :); **otherwise the returned value contains the what() string. *Otherwise, the boost:: + 1 + + 0 + + -5 + + + 2 + template is not available. The string representation of each (:link + 1 + + 0 + + -44 + + + 2 + :) object is deduced by a function call that is bound at the time the (:link + 1 + + 0 + + -44 + + + 2 + :)<Tag,T> template is instantiated. The following overload resolutions are attempted in order: #Unqualified call to to_string(x), where x is of type (:link + 1 + + 0 + + -44 + + + 2 + :)<Tag,T> (the return value is expected to be of type std::string.) #Unqualified call to to_string(x.(:link + 1 + + 0 + + -32 + + + 2 + mod="m":)()) (the return value is expected to be of type std::string.) #Unqualified call to s << x.(:link + 1 + + 0 + + -32 + + + 2 + mod="m":)(), where s is a std::ostringstream. The first successfully bound function is used at the time (:link + 1 + + 0 + + -5 + + + 2 + :) is called; if all 3 overload resolutions are unsuccessful, the system is unable to convert the (:link + 1 + + 0 + + -44 + + + 2 + :) object to string, and ''an unspecified stub string value is used without issuing a compile error.'' !!!!Notes: *The format of the returned string is unspecified. *The returned string is ''not'' user-friendly. *The returned string may include additional platform-specific diagnostic information. (:include + 1 + + 0 + + -34 + + + 2 + :) + + + + + 0 + + -6 + + + + 29 + 2 + (:auto !!!:) (:include synopsis:) !!!!Requirements: The (:link + 1 + + 0 + + -6 + + + 2 + :) function must not be called outside of a catch block. !!!!Returns: * An (:link + 1 + + 0 + + -24 + + + 2 + :) that refers to the currently handled exception or a copy of the currently handled exception. * If the function needs to allocate memory and the attempt fails, it returns an (:link + 1 + + 0 + + -24 + + + 2 + :) that refers to an instance of std::bad_alloc. !!!!Throws: Nothing. !!!!Notes: * It is unspecified whether the return values of two successive calls to (:link + 1 + + 0 + + -6 + + + 2 + :) refer to the same exception object. * Correct implementation of (:link + 1 + + 0 + + -6 + + + 2 + :) may require compiler support, unless (:link + 1 + + 0 + + -8 + + + 2 + :) was used at the time the currently handled exception object was passed to throw. If (:link + 1 + + 0 + + -8 + + + 2 + :) was not used, and if the compiler does not provide the necessary support, then (:link + 1 + + 0 + + -6 + + + 2 + :) may return an (:link + 1 + + 0 + + -24 + + + 2 + :) that refers to an instance of (:link + 1 + + 0 + + -36 + + + 2 + :). In this case, if the original exception object derives from boost::(:link + 1 + + 0 + + -43 + + + 2 + :), then the boost::(:link + 1 + + 0 + + -43 + + + 2 + :) sub-object of the (:link + 1 + + 0 + + -36 + + + 2 + :) object is initialized by the boost::(:link + 1 + + 0 + + -43 + + + 2 + :) copy constructor. + + + + + 0 + + -7 + + 19 2 @@ -5280,7 +5558,7 @@ 0 - -36 + -37 2 @@ -5289,7 +5567,7 @@ 0 - -36 + -37 2 @@ -5298,7 +5576,7 @@ 0 - -42 + -43 2 @@ -5307,7 +5585,7 @@ 0 - -25 + -8 2 @@ -5316,7 +5594,7 @@ 0 - -21 + -23 2 @@ -5325,7 +5603,7 @@ 0 - -39 + -40 2 @@ -5343,7 +5621,7 @@ 0 - -39 + -40 2 @@ -5352,7 +5630,7 @@ 0 - -6 + -5 2 @@ -5363,58 +5641,40 @@ 0 - -6 + -8 - 29 + 21 2 - (:auto !!!:) (:include synopsis:) !!!!Returns: A string value that contains varying amount of implementation-specific diagnostic information about the passed exception object: *If E can be statically converted to boost::(:link + (:auto !!!:) (:include synopsis:) !!!!Requirements: T must be a class with an accessible no-throw copy constructor. !!!!Returns: An object of ''unspecified'' type which derives publicly from T. That is, the returned object can be intercepted by a catch(T &). !!!!Description: This function is designed to be used directly in a throw-expression to enable the (:link 1 0 - -42 + -24 2 - :), the returned value contains the string representations of all (:link + :) support in Boost Exception. For example: [@class my_exception: public std::exception { }; .... throw boost::(:link 1 0 - -43 + -8 2 - :) objects stored in the boost::(:link + :)(my_exception());@] Unless (:link 1 0 - -42 + -8 2 - :) through (:link - 1 - - 0 - - -17 - - - 2 - mod="/":), along with other diagnostic information relevant to the exception. If e can be dynamically converted to std::exception, the returned value also contains the what() string. *Otherwise, if E can be statically converted std::exception: **if e can be dynamically converted to boost::exception, the returned value is the same as if E could be statically converted to boost::(:link - 1 - - 0 - - -42 - - - 2 - :); **otherwise the returned value contains the what() string. *Otherwise, the boost:: + :) is called at the time an exception object is used in a throw-expression, an attempt to copy it using (:link 1 0 @@ -5423,52 +5683,25 @@ 2 - template is not available. The string representation of each (:link + :) may return an (:link 1 0 - -43 + -24 2 - :) object is deduced by a function call that is bound at the time the (:link + :) which refers to an instance of (:link 1 0 - -43 + -36 2 - :)<Tag,T> template is instantiated. The following overload resolutions are attempted in order: #Unqualified call to to_string(x), where x is of type (:link - 1 - - 0 - - -43 - - - 2 - :)<Tag,T> (the return value is expected to be of type std::string.) #Unqualified call to to_string(x.(:link - 1 - - 0 - - -31 - - - 2 - mod="m":)()) (the return value is expected to be of type std::string.) #Unqualified call to s << x.(:link - 1 - - 0 - - -31 - - - 2 - mod="m":)(), where s is a std::ostringstream. The first successfully bound function is used at the time (:link + :). See (:link 1 0 @@ -5477,7 +5710,16 @@ 2 - :) is called; if all 3 overload resolutions are unsuccessful, the system is unable to convert the (:link + :) for details. !!!!Note: Instead of using the throw keyword directly, it is preferable to call boost::(:link + 1 + + 0 + + -40 + + + 2 + :). This is guaranteed to throw an exception that derives from boost::(:link 1 0 @@ -5486,23 +5728,23 @@ 2 - :) object to string, and ''an unspecified stub string value is used without issuing a compile error.'' !!!!Notes: *The format of the returned string is unspecified. *The returned string is ''not'' user-friendly. *The returned string may include additional platform-specific diagnostic information. (:include + :) and supports the (:link 1 0 - -33 + -24 2 - :) + :) functionality. 0 - -7 + -9 @@ -5513,7 +5755,7 @@ 0 - -8 + -6 2 @@ -5522,7 +5764,7 @@ 0 - -22 + -24 2 @@ -5540,7 +5782,7 @@ 0 - -42 + -43 2 @@ -5549,7 +5791,7 @@ 0 - -22 + -24 2 @@ -5558,7 +5800,7 @@ 0 - -22 + -24 2 @@ -5567,7 +5809,7 @@ 0 - -8 + -6 2 @@ -5576,7 +5818,7 @@ 0 - -8 + -6 2 @@ -5585,7 +5827,7 @@ 0 - -40 + -41 2 @@ -5594,7 +5836,7 @@ 0 - -22 + -24 2 @@ -5603,7 +5845,7 @@ 0 - -40 + -41 2 @@ -5612,7 +5854,7 @@ 0 - -8 + -6 2 @@ -5621,7 +5863,7 @@ 0 - -22 + -24 2 @@ -5630,7 +5872,7 @@ 0 - -25 + -8 2 @@ -5639,7 +5881,7 @@ 0 - -22 + -24 2 @@ -5648,7 +5890,7 @@ 0 - -35 + -36 2 @@ -5657,7 +5899,7 @@ 0 - -8 + -6 2 @@ -5666,174 +5908,13 @@ 0 - -40 + -41 2 :) in the above examples is well-formed. - - - 0 - - -8 - - - - 29 - 2 - (:auto !!!:) (:include synopsis:) !!!!Requirements: The (:link - 1 - - 0 - - -8 - - - 2 - :) function must not be called outside of a catch block. !!!!Returns: * An (:link - 1 - - 0 - - -22 - - - 2 - :) that refers to the currently handled exception or a copy of the currently handled exception. * If the function needs to allocate memory and the attempt fails, it returns an (:link - 1 - - 0 - - -22 - - - 2 - :) that refers to an instance of std::bad_alloc. !!!!Throws: Nothing. !!!!Notes: * It is unspecified whether the return values of two successive calls to (:link - 1 - - 0 - - -8 - - - 2 - :) refer to the same exception object. * Correct implementation of (:link - 1 - - 0 - - -8 - - - 2 - :) may require compiler support, unless (:link - 1 - - 0 - - -25 - - - 2 - :) was used at the time the currently handled exception object was passed to throw. If (:link - 1 - - 0 - - -25 - - - 2 - :) was not used, and if the compiler does not provide the necessary support, then (:link - 1 - - 0 - - -8 - - - 2 - :) may return an (:link - 1 - - 0 - - -22 - - - 2 - :) that refers to an instance of (:link - 1 - - 0 - - -35 - - - 2 - :). In this case, if the original exception object derives from boost::(:link - 1 - - 0 - - -42 - - - 2 - :), then the boost::(:link - 1 - - 0 - - -42 - - - 2 - :) sub-object of the (:link - 1 - - 0 - - -35 - - - 2 - :) object is initialized by the boost::(:link - 1 - - 0 - - -42 - - - 2 - :) copy constructor. - - - - - 0 - - -9 - - - - 3 - 2 - (:auto !!!:) (:include synopsis:) !!!!Effects: Stores a copy of v in the - 1 - - 0 - - -43 - - - 2 - object. (:include throws:) - - 0 @@ -5841,139 +5922,6 @@ -10 - - 5 - 2 - (:auto !!!:) (:include synopsis:) !!!!Requirements: E must be boost::(:link - 1 - - 0 - - -42 - - - 2 - :), or a type that derives (indirectly) from boost::(:link - 1 - - 0 - - -42 - - - 2 - :). !!!!Effects: Equivalent to x << v.(:link http://www.boost.org/libs/tuple/doc/tuple_users_guide.html#accessing_elements|get:)<0>() << ... << v.(:link http://www.boost.org/libs/tuple/doc/tuple_users_guide.html#accessing_elements|get:)<N>(). !!!!Returns: x. (:include throws:) - - - - - 0 - - -11 - - - - 11 - 2 - (:auto !!:) All exception types that derive from boost::(:link - 1 - - 0 - - -42 - - - 2 - :) can be used as type-safe containers of arbitrary data objects, while complying with the no-throw requirements (15.5.1) of the ANSI C++ standard for exception types. When exceptions derive from boost::(:link - 1 - - 0 - - -42 - - - 2 - :), arbitrary data can be added to exception objects: *At the point of the throw; *At a later time as exceptions bubble up the call stack. (:include - 1 - - 0 - - -45 - - - 2 - :) (:include - 1 - - 0 - - -29 - - - 2 - :) (:include - 1 - - 0 - - -24 - - - 2 - :) - - - - - 0 - - -12 - - - - 1 - 2 - (:auto !!:) !!!Synopsis (:include synopsis:) - - - - - 0 - - -13 - - - - 5 - 2 - (:auto !!!:) (:include synopsis:) !!!!Effects: As if [@try { throw - 1 - - 0 - - -25 - - - 2 - (e); } catch(...) { return (:link - 1 - - 0 - - -8 - - - 2 - :)(); }@] - - - - - 0 - - -14 - - 19 2 @@ -5982,7 +5930,7 @@ 0 - -6 + -5 2 @@ -5991,7 +5939,7 @@ 0 - -42 + -43 2 @@ -6000,7 +5948,7 @@ 0 - -42 + -43 2 @@ -6009,7 +5957,7 @@ 0 - -17 + -18 2 @@ -6027,7 +5975,7 @@ 0 - -42 + -43 2 @@ -6036,7 +5984,7 @@ 0 - -42 + -43 2 @@ -6045,7 +5993,7 @@ 0 - -6 + -5 2 @@ -6054,7 +6002,7 @@ 0 - -33 + -34 2 @@ -6065,7 +6013,118 @@ 0 - -15 + -11 + + + + 3 + 2 + (:auto !!!:) (:include synopsis:) !!!!Effects: Stores a copy of v in the + 1 + + 0 + + -44 + + + 2 + object. (:include throws:) + + + + + 0 + + -12 + + + + 5 + 2 + (:auto !!!:) (:include synopsis:) !!!!Requirements: E must be boost::(:link + 1 + + 0 + + -43 + + + 2 + :), or a type that derives (indirectly) from boost::(:link + 1 + + 0 + + -43 + + + 2 + :). !!!!Effects: Equivalent to x << v.(:link http://www.boost.org/libs/tuple/doc/tuple_users_guide.html#accessing_elements|get:)<0>() << ... << v.(:link http://www.boost.org/libs/tuple/doc/tuple_users_guide.html#accessing_elements|get:)<N>(). !!!!Returns: x. (:include throws:) + + + + + 0 + + -13 + + + + 11 + 2 + (:auto !!:) All exception types that derive from boost::(:link + 1 + + 0 + + -43 + + + 2 + :) can be used as type-safe containers of arbitrary data objects, while complying with the no-throw requirements (15.5.1) of the ANSI C++ standard for exception types. When exceptions derive from boost::(:link + 1 + + 0 + + -43 + + + 2 + :), arbitrary data can be added to exception objects: *At the point of the throw; *At a later time as exceptions bubble up the call stack. (:include + 1 + + 0 + + -46 + + + 2 + :) (:include + 1 + + 0 + + -30 + + + 2 + :) (:include + 1 + + 0 + + -26 + + + 2 + :) + + + + + 0 + + -14 @@ -6078,139 +6137,13 @@ 0 - -16 + -15 - 65 + 5 2 - (:auto !!:) !!!Why doesn't boost::exception derive from std::exception? Despite that (:link - 1 - - 0 - - -41 - - - 2 - |virtual inheritance should be used in deriving from base exception types:), many programmers fail to follow this principle when deriving from std::exception. If boost::(:link - 1 - - 0 - - -42 - - - 2 - :) derives from std::exception, using the (:link - 1 - - 0 - - -21 - - - 2 - :) function with such user-defined types would introduce dangerous ambiguity which would break all catch(std::exception &) statements. Of course, boost::(:link - 1 - - 0 - - -42 - - - 2 - :) should not be used to replace std::exception as a base type in exception type hierarchies. Instead, it should be included as a virtual base, in addition to std::exception (which should also be derived virtually.) !!!Why is boost::exception abstract? To prevent exception-neutral contexts from erroneously erasing the type of the original exception when adding (:link - 1 - - 0 - - -43 - - - 2 - :) to an active exception object: [@catch( boost::(:link - 1 - - 0 - - -42 - - - 2 - :) & e ) { e (:link - 1 - - 0 - - -17 - - - 2 - |<<:) foo_info(foo); throw e; //Compile error: boost::(:link - 1 - - 0 - - -42 - - - 2 - :) is abstract }@] The correct code is: [@catch( boost::(:link - 1 - - 0 - - -42 - - - 2 - :) & e ) { e (:link - 1 - - 0 - - -17 - - - 2 - |<<:) foo_info(foo); throw; //Okay, re-throwing the original exception object. }@] !!!What is the space overhead of the boost::exception base class? The space overhead for the boost::exception data members is negligible in the context of exception handling. Throwing objects that derive from boost::(:link - 1 - - 0 - - -42 - - - 2 - :) does not by itself cause dynamic memory allocations. Deriving from boost::(:link - 1 - - 0 - - -42 - - - 2 - :) enables any data to be added to exceptions, which usually does allocate memory. However, this memory is reclaimed when the exception has been handled, and since typically user code does not allocate memory during the unrolling of the stack, adding error info to exceptions should not cause memory fragmentation. !!!Should I use boost::throw_exception or BOOST_THROW_EXCEPTION or just throw? The benefit of calling boost::(:link - 1 - - 0 - - -39 - - - 2 - :) instead of using throw directly is that it ensures that the emitted exception derives from boost::(:link - 1 - - 0 - - -42 - - - 2 - :) and that it is compatible with boost::(:link + (:auto !!!:) (:include synopsis:) !!!!Effects: As if [@try { throw 1 0 @@ -6219,25 +6152,7 @@ 2 - :). The (:link - 1 - - 0 - - -26 - - - 2 - :) macro also results in a call to boost::(:link - 1 - - 0 - - -39 - - - 2 - :), but in addition it records in the exception object the __FILE__ and __LINE__ of the throw, as well as the pretty name of the function that throws. This has virtually no overhead, yet enables boost::(:link + (e); } catch(...) { return (:link 1 0 @@ -6246,133 +6161,20 @@ 2 - :) to compose a more useful, if not user-friendly message. Typical use of boost::(:link - 1 - - 0 - - -6 - - + :)(); }@] + + + + + 0 + + -16 + + + + 1 2 - :) is: [@catch( boost::exception & e ) { std::cerr << "OMG!" << boost::diagnostic_information(e); } catch( ... ) { std::cerr << "OMG!!!"; }@] This is a possible message it may display, the first line is only possible if (:link - 1 - - 0 - - -26 - - - 2 - :) is used: [@example_io.cpp(83): Throw in function void parse_file(const char *) Dynamic exception type: class file_open_error std::exception::what: example_io error [struct tag_errno_code *] = 2, OS says "No such file or directory" [struct tag_file_name *] = tmp1.xml [struct tag_function *] = fopen [struct tag_open_mode *] = rb@] !!!Why is boost::exception integrated in boost::throw_exception? The boost::(:link - 1 - - 0 - - -39 - - - 2 - :) function predates the Boost Exception library and there has been some concern about its current behavior of injecting boost::(:link - 1 - - 0 - - -42 - - - 2 - :) as a base of any exception passed to boost::(:link - 1 - - 0 - - -39 - - - 2 - :). Such concerns are dictated by the typical strict interpretation of a common principle in C and C++, that users only pay for features they actually use. The problem is that users of Boost Exception can't by themselves cause a library to throw types that derive from boost::(:link - 1 - - 0 - - -42 - - - 2 - :), and without this they can't use any of the Boost Exception facilities. For example, if a user wants to use Boost Serialization in a separate thread, it is desirable to be able to transport exceptions emitted by that library into the main thread where they can be analyzed to generate a user-friendly message. This can be easily achieved using boost::(:link - 1 - - 0 - - -22 - - - 2 - :), but this requires that Boost Serialization throws exceptions using boost::(:link - 1 - - 0 - - -25 - - - 2 - :). If Boost Serialization calls boost::(:link - 1 - - 0 - - -39 - - - 2 - :) to throw, this behavior happens automatically and transparently. The cost of this integration is: * In terms of space: a pointer and 3 ints are added to the static size of exception objects. * In terms of speed: the pointer is initialized to null at the point of the throw. * In terms of coupling: about 400 self-contained lines of C++ with no external includes. !!!Why use operator<< overload for adding info to exceptions? Before throwing an object of type that derives from boost::(:link - 1 - - 0 - - -42 - - - 2 - :), it is often desirable to add one or more (:link - 1 - - 0 - - -43 - - - 2 - :) objects in it. The syntactic sugar provided by (:link - 1 - - 0 - - -17 - - - 2 - :) allows this to be done directly in a throw expression: [@throw error() (:link - 1 - - 0 - - -17 - - - 2 - |<<:) foo_info(foo) (:link - 1 - - 0 - - -17 - - - 2 - |<<:) bar_info(bar);@] which saves typing compared to this possible alternative: [@error e; e.add(foo_info(foo)); e.add(bar_info(bar)); throw e;@] and looks better than something like: [@throw error().add(foo_info(foo)).add(bar_info(bar));@] + (:auto !!:) !!!Synopsis (:include synopsis:) @@ -6383,9 +6185,9 @@ - 7 + 65 2 - (:auto !!!:) (:include synopsis:) !!!!Requirements: E must be boost::(:link + (:auto !!:) !!!Why doesn't boost::exception derive from std::exception? Despite that (:link 1 0 @@ -6394,16 +6196,7 @@ 2 - :), or a type that derives (indirectly) from boost::(:link - 1 - - 0 - - -42 - - - 2 - :). !!!!Effects: Stores a copy of v into x. If x already contains data of type (:link + |virtual inheritance should be used in deriving from base exception types:), many programmers fail to follow this principle when deriving from std::exception. If boost::(:link 1 0 @@ -6412,7 +6205,277 @@ 2 - :)<Tag,T>, that data is overwritten. !!!!Returns: x. (:include throws:) + :) derives from std::exception, using the (:link + 1 + + 0 + + -23 + + + 2 + :) function with such user-defined types would introduce dangerous ambiguity which would break all catch(std::exception &) statements. Of course, boost::(:link + 1 + + 0 + + -43 + + + 2 + :) should not be used to replace std::exception as a base type in exception type hierarchies. Instead, it should be included as a virtual base, in addition to std::exception (which should also be derived virtually.) !!!Why is boost::exception abstract? To prevent exception-neutral contexts from erroneously erasing the type of the original exception when adding (:link + 1 + + 0 + + -44 + + + 2 + :) to an active exception object: [@catch( boost::(:link + 1 + + 0 + + -43 + + + 2 + :) & e ) { e (:link + 1 + + 0 + + -18 + + + 2 + |<<:) foo_info(foo); throw e; //Compile error: boost::(:link + 1 + + 0 + + -43 + + + 2 + :) is abstract }@] The correct code is: [@catch( boost::(:link + 1 + + 0 + + -43 + + + 2 + :) & e ) { e (:link + 1 + + 0 + + -18 + + + 2 + |<<:) foo_info(foo); throw; //Okay, re-throwing the original exception object. }@] !!!What is the space overhead of the boost::exception base class? The space overhead for the boost::exception data members is negligible in the context of exception handling. Throwing objects that derive from boost::(:link + 1 + + 0 + + -43 + + + 2 + :) does not by itself cause dynamic memory allocations. Deriving from boost::(:link + 1 + + 0 + + -43 + + + 2 + :) enables any data to be added to exceptions, which usually does allocate memory. However, this memory is reclaimed when the exception has been handled, and since typically user code does not allocate memory during the unrolling of the stack, adding error info to exceptions should not cause memory fragmentation. !!!Should I use boost::throw_exception or BOOST_THROW_EXCEPTION or just throw? The benefit of calling boost::(:link + 1 + + 0 + + -40 + + + 2 + :) instead of using throw directly is that it ensures that the emitted exception derives from boost::(:link + 1 + + 0 + + -43 + + + 2 + :) and that it is compatible with boost::(:link + 1 + + 0 + + -6 + + + 2 + :). The (:link + 1 + + 0 + + -27 + + + 2 + :) macro also results in a call to boost::(:link + 1 + + 0 + + -40 + + + 2 + :), but in addition it records in the exception object the __FILE__ and __LINE__ of the throw, as well as the pretty name of the function that throws. This has virtually no overhead, yet enables boost::(:link + 1 + + 0 + + -5 + + + 2 + :) to compose a more useful, if not user-friendly message. Typical use of boost::(:link + 1 + + 0 + + -5 + + + 2 + :) is: [@catch( boost::exception & e ) { std::cerr << "OMG!" << boost::diagnostic_information(e); } catch( ... ) { std::cerr << "OMG!!!"; }@] This is a possible message it may display, the first line is only possible if (:link + 1 + + 0 + + -27 + + + 2 + :) is used: [@example_io.cpp(83): Throw in function void parse_file(const char *) Dynamic exception type: class file_open_error std::exception::what: example_io error [struct tag_errno_code *] = 2, OS says "No such file or directory" [struct tag_file_name *] = tmp1.xml [struct tag_function *] = fopen [struct tag_open_mode *] = rb@] !!!Why is boost::exception integrated in boost::throw_exception? The boost::(:link + 1 + + 0 + + -40 + + + 2 + :) function predates the Boost Exception library and there has been some concern about its current behavior of injecting boost::(:link + 1 + + 0 + + -43 + + + 2 + :) as a base of any exception passed to boost::(:link + 1 + + 0 + + -40 + + + 2 + :). Such concerns are dictated by the typical strict interpretation of a common principle in C and C++, that users only pay for features they actually use. The problem is that users of Boost Exception can't by themselves cause a library to throw types that derive from boost::(:link + 1 + + 0 + + -43 + + + 2 + :), and without this they can't use any of the Boost Exception facilities. For example, if a user wants to use Boost Serialization in a separate thread, it is desirable to be able to transport exceptions emitted by that library into the main thread where they can be analyzed to generate a user-friendly message. This can be easily achieved using boost::(:link + 1 + + 0 + + -24 + + + 2 + :), but this requires that Boost Serialization throws exceptions using boost::(:link + 1 + + 0 + + -8 + + + 2 + :). If Boost Serialization calls boost::(:link + 1 + + 0 + + -40 + + + 2 + :) to throw, this behavior happens automatically and transparently. The cost of this integration is: * In terms of space: a pointer and 3 ints are added to the static size of exception objects. * In terms of speed: the pointer is initialized to null at the point of the throw. * In terms of coupling: about 400 self-contained lines of C++ with no external includes. !!!Why use operator<< overload for adding info to exceptions? Before throwing an object of type that derives from boost::(:link + 1 + + 0 + + -43 + + + 2 + :), it is often desirable to add one or more (:link + 1 + + 0 + + -44 + + + 2 + :) objects in it. The syntactic sugar provided by (:link + 1 + + 0 + + -18 + + + 2 + :) allows this to be done directly in a throw expression: [@throw error() (:link + 1 + + 0 + + -18 + + + 2 + |<<:) foo_info(foo) (:link + 1 + + 0 + + -18 + + + 2 + |<<:) bar_info(bar);@] which saves typing compared to this possible alternative: [@error e; e.add(foo_info(foo)); e.add(bar_info(bar)); throw e;@] and looks better than something like: [@throw error().add(foo_info(foo)).add(bar_info(bar));@] @@ -6423,27 +6486,9 @@ - 33 + 7 2 - (:auto !!!:) Traditionally, when using exceptions to report failures, the throw site: *creates an exception object of the appropriate type, and *stuffs it with data relevant to the detected error. A higher context in the program contains a catch statement which: *selects failures based on exception types, and *inspects exception objects for data required to deal with the problem. The main issue with this "traditional" approach is that often, the data available at the point of the throw is insufficient for the catch site to handle the failure. Here is an example of a catch statement: [@catch( file_read_error & e ) { std::cerr << e.file_name(); }@] And here is a possible matching throw: [@void read_file( FILE * f ) { .... size_t nr=fread(buf,1,count,f); if( ferror(f) ) throw file_read_error(???); .... }@] Clearly, the problem is that the handler requires a file name but the read_file function does not have a file name to put in the exception object; all it has is a FILE pointer! In an attempt to deal with this problem, we could modify read_file to accept a file name: [@void read_file( FILE * f, char const * name ) { .... size_t nr=fread(buf,1,count,f); if( ferror(f) ) throw file_read_error(name); .... }@] This is not a real solution: it simply shifts the burden of supplying a file name to the immediate caller of the read_file function. ->''In general, the data required to handle a given library-emitted exception depends on the program that links to it. Many contexts between the throw and the catch may have relevant information which must be transported to the exception handler.'' !!!Exception wrapping The idea of exception wrapping is to catch an exception from a lower level function (such as the read_file function above), and throw a new exception object that contains the original exception (and also carries a file name.) This method seems to be particularly popular with C++ programmers with Java background. Exception wrapping leads to the following problems: *To wrap an exception object it must be copied, which may result in slicing. *Wrapping is practically impossible to use in generic contexts. The second point is actually special case of violating the exception neutrality principle. Most contexts in a program can not handle exceptions; such contexts should not interfere with the process of exception handling. !!!The boost::exception solution *Simply derive your exception types from boost::(:link - 1 - - 0 - - -42 - - - 2 - :). *Confidently limit the throw site to provide only data that is available naturally. *Use exception-neutral contexts between the throw and the catch to augment exceptions with more relevant data as they bubble up. For example, in the throw statement below we only add the errno code, since this is the only failure-relevant information available in this context: [@struct exception_base: virtual std::exception, virtual boost::(:link - 1 - - 0 - - -42 - - - 2 - :) { }; struct io_error: virtual exception_base { }; struct file_read_error: virtual io_error { }; typedef boost::(:link + (:auto !!!:) (:include synopsis:) !!!!Requirements: E must be boost::(:link 1 0 @@ -6452,25 +6497,7 @@ 2 - :)<struct tag_errno_code,int> errno_code; void read_file( FILE * f ) { .... size_t nr=fread(buf,1,count,f); if( ferror(f) ) throw file_read_error() (:link - 1 - - 0 - - -17 - - - 2 - |<<:) errno_code(errno); .... }@] In a higher exception-neutral context, we add the file name to ''any'' exception that derives from boost::(:link - 1 - - 0 - - -42 - - - 2 - :): [@typedef boost::(:link + :), or a type that derives (indirectly) from boost::(:link 1 0 @@ -6479,97 +6506,16 @@ 2 - :)<struct tag_file_name,std::string> file_name; .... try { if( FILE * fp=fopen("foo.txt","rt") ) { shared_ptr<FILE> f(fp,fclose); .... read_file(fp); //throws types deriving from boost::(:link + :). !!!!Effects: Stores a copy of v into x. If x already contains data of type (:link 1 0 - -42 + -44 2 - :) do_something(); .... } else throw file_open_error() (:link - 1 - - 0 - - -17 - - - 2 - |<<:) errno_code(errno); } catch( boost::(:link - 1 - - 0 - - -42 - - - 2 - :) & e ) { e (:link - 1 - - 0 - - -17 - - - 2 - |<<:) file_name("foo.txt"); throw; }@] Finally here is how the handler retrieves data from exceptions that derive from boost::(:link - 1 - - 0 - - -42 - - - 2 - :): [@catch( io_error & e ) { std::cerr << "I/O Error!\n"; if( std::string const * fn=(:link - 1 - - 0 - - -36 - - - 2 - :)<file_name>(e) ) std::cerr << "File name: " << *fn << "\n"; if( int const * c=(:link - 1 - - 0 - - -36 - - - 2 - :)<errno_code>(e) ) std::cerr << "OS says: " << strerror(*c) << "\n"; }@] In addition, boost::(:link - 1 - - 0 - - -6 - - - 2 - :) can be used to compose an automatic (if not user-friendly) message that contains all of the (:link - 1 - - 0 - - -43 - - - 2 - :) objects added to a boost::(:link - 1 - - 0 - - -42 - - - 2 - :). This is useful for inclusion in logs and other diagnostic objects. + :)<Tag,T>, that data is overwritten. !!!!Returns: x. (:include throws:) @@ -6580,36 +6526,9 @@ - 7 + 1 2 - (:auto !!!:) Deriving from boost::(:link - 1 - - 0 - - -42 - - - 2 - :) effectively decouples the semantics of a failure from the information that is relevant to each individual instance of reporting a failure with a given semantic. In other words: with boost::(:link - 1 - - 0 - - -42 - - - 2 - :), what data a given exception object transports depends primarily on the context in which failures are reported (not on its type.) Since exception types need no members, it becomes very natural to throw exceptions that derive from more than one type to indicate multiple appropriate semantics: [@struct exception_base: virtual std::exception, virtual boost::(:link - 1 - - 0 - - -42 - - - 2 - :) { }; struct io_error: virtual exception_base { }; struct file_error: virtual io_error { }; struct read_error: virtual io_error { }; struct file_read_error: virtual file_error, virtual read_error { };@] Using this approach, exception types become a simple tagging system for categorizing errors and selecting failures in exception handlers. + (:auto !!!:) !!!Synopsis (:include synopsis:) @@ -6619,6 +6538,203 @@ -20 + + 33 + 2 + (:auto !!!:) Traditionally, when using exceptions to report failures, the throw site: *creates an exception object of the appropriate type, and *stuffs it with data relevant to the detected error. A higher context in the program contains a catch statement which: *selects failures based on exception types, and *inspects exception objects for data required to deal with the problem. The main issue with this "traditional" approach is that often, the data available at the point of the throw is insufficient for the catch site to handle the failure. Here is an example of a catch statement: [@catch( file_read_error & e ) { std::cerr << e.file_name(); }@] And here is a possible matching throw: [@void read_file( FILE * f ) { .... size_t nr=fread(buf,1,count,f); if( ferror(f) ) throw file_read_error(???); .... }@] Clearly, the problem is that the handler requires a file name but the read_file function does not have a file name to put in the exception object; all it has is a FILE pointer! In an attempt to deal with this problem, we could modify read_file to accept a file name: [@void read_file( FILE * f, char const * name ) { .... size_t nr=fread(buf,1,count,f); if( ferror(f) ) throw file_read_error(name); .... }@] This is not a real solution: it simply shifts the burden of supplying a file name to the immediate caller of the read_file function. ->''In general, the data required to handle a given library-emitted exception depends on the program that links to it. Many contexts between the throw and the catch may have relevant information which must be transported to the exception handler.'' !!!Exception wrapping The idea of exception wrapping is to catch an exception from a lower level function (such as the read_file function above), and throw a new exception object that contains the original exception (and also carries a file name.) This method seems to be particularly popular with C++ programmers with Java background. Exception wrapping leads to the following problems: *To wrap an exception object it must be copied, which may result in slicing. *Wrapping is practically impossible to use in generic contexts. The second point is actually special case of violating the exception neutrality principle. Most contexts in a program can not handle exceptions; such contexts should not interfere with the process of exception handling. !!!The boost::exception solution *Simply derive your exception types from boost::(:link + 1 + + 0 + + -43 + + + 2 + :). *Confidently limit the throw site to provide only data that is available naturally. *Use exception-neutral contexts between the throw and the catch to augment exceptions with more relevant data as they bubble up. For example, in the throw statement below we only add the errno code, since this is the only failure-relevant information available in this context: [@struct exception_base: virtual std::exception, virtual boost::(:link + 1 + + 0 + + -43 + + + 2 + :) { }; struct io_error: virtual exception_base { }; struct file_read_error: virtual io_error { }; typedef boost::(:link + 1 + + 0 + + -44 + + + 2 + :)<struct tag_errno_code,int> errno_code; void read_file( FILE * f ) { .... size_t nr=fread(buf,1,count,f); if( ferror(f) ) throw file_read_error() (:link + 1 + + 0 + + -18 + + + 2 + |<<:) errno_code(errno); .... }@] In a higher exception-neutral context, we add the file name to ''any'' exception that derives from boost::(:link + 1 + + 0 + + -43 + + + 2 + :): [@typedef boost::(:link + 1 + + 0 + + -44 + + + 2 + :)<struct tag_file_name,std::string> file_name; .... try { if( FILE * fp=fopen("foo.txt","rt") ) { shared_ptr<FILE> f(fp,fclose); .... read_file(fp); //throws types deriving from boost::(:link + 1 + + 0 + + -43 + + + 2 + :) do_something(); .... } else throw file_open_error() (:link + 1 + + 0 + + -18 + + + 2 + |<<:) errno_code(errno); } catch( boost::(:link + 1 + + 0 + + -43 + + + 2 + :) & e ) { e (:link + 1 + + 0 + + -18 + + + 2 + |<<:) file_name("foo.txt"); throw; }@] Finally here is how the handler retrieves data from exceptions that derive from boost::(:link + 1 + + 0 + + -43 + + + 2 + :): [@catch( io_error & e ) { std::cerr << "I/O Error!\n"; if( std::string const * fn=(:link + 1 + + 0 + + -37 + + + 2 + :)<file_name>(e) ) std::cerr << "File name: " << *fn << "\n"; if( int const * c=(:link + 1 + + 0 + + -37 + + + 2 + :)<errno_code>(e) ) std::cerr << "OS says: " << strerror(*c) << "\n"; }@] In addition, boost::(:link + 1 + + 0 + + -5 + + + 2 + :) can be used to compose an automatic (if not user-friendly) message that contains all of the (:link + 1 + + 0 + + -44 + + + 2 + :) objects added to a boost::(:link + 1 + + 0 + + -43 + + + 2 + :). This is useful for inclusion in logs and other diagnostic objects. + + + + + 0 + + -21 + + + + 7 + 2 + (:auto !!!:) Deriving from boost::(:link + 1 + + 0 + + -43 + + + 2 + :) effectively decouples the semantics of a failure from the information that is relevant to each individual instance of reporting a failure with a given semantic. In other words: with boost::(:link + 1 + + 0 + + -43 + + + 2 + :), what data a given exception object transports depends primarily on the context in which failures are reported (not on its type.) Since exception types need no members, it becomes very natural to throw exceptions that derive from more than one type to indicate multiple appropriate semantics: [@struct exception_base: virtual std::exception, virtual boost::(:link + 1 + + 0 + + -43 + + + 2 + :) { }; struct io_error: virtual exception_base { }; struct file_error: virtual io_error { }; struct read_error: virtual io_error { }; struct file_read_error: virtual file_error, virtual read_error { };@] Using this approach, exception types become a simple tagging system for categorizing errors and selecting failures in exception handlers. + + + + + 0 + + -22 + + 27 2 @@ -6627,7 +6743,7 @@ 0 - -42 + -43 2 @@ -6636,7 +6752,7 @@ 0 - -21 + -23 2 @@ -6645,7 +6761,7 @@ 0 - -42 + -43 2 @@ -6663,7 +6779,7 @@ 0 - -43 + -44 2 @@ -6672,7 +6788,7 @@ 0 - -43 + -44 2 @@ -6681,7 +6797,7 @@ 0 - -43 + -44 2 @@ -6690,7 +6806,7 @@ 0 - -21 + -23 2 @@ -6699,7 +6815,7 @@ 0 - -21 + -23 2 @@ -6708,7 +6824,7 @@ 0 - -42 + -43 2 @@ -6717,7 +6833,7 @@ 0 - -17 + -18 2 @@ -6726,7 +6842,7 @@ 0 - -42 + -43 2 @@ -6735,7 +6851,7 @@ 0 - -11 + -13 2 @@ -6746,7 +6862,7 @@ 0 - -21 + -23 @@ -6757,7 +6873,7 @@ 0 - -42 + -43 2 @@ -6766,7 +6882,7 @@ 0 - -42 + -43 2 @@ -6777,7 +6893,7 @@ 0 - -22 + -24 @@ -6788,7 +6904,7 @@ 0 - -22 + -24 2 @@ -6797,7 +6913,7 @@ 0 - -22 + -24 2 @@ -6806,7 +6922,7 @@ 0 - -22 + -24 2 @@ -6815,7 +6931,7 @@ 0 - -22 + -24 2 @@ -6824,7 +6940,7 @@ 0 - -22 + -24 2 @@ -6833,7 +6949,7 @@ 0 - -22 + -24 2 @@ -6842,7 +6958,7 @@ 0 - -8 + -6 2 @@ -6851,7 +6967,7 @@ 0 - -40 + -41 2 @@ -6862,7 +6978,7 @@ 0 - -23 + -25 @@ -6873,7 +6989,7 @@ 0 - -42 + -43 2 @@ -6884,7 +7000,7 @@ 0 - -24 + -26 @@ -6904,7 +7020,7 @@ 0 - -43 + -44 2 @@ -6913,7 +7029,7 @@ 0 - -43 + -44 2 @@ -6922,7 +7038,7 @@ 0 - -43 + -44 2 @@ -6931,7 +7047,7 @@ 0 - -42 + -43 2 @@ -6940,7 +7056,7 @@ 0 - -36 + -37 2 @@ -6951,110 +7067,7 @@ 0 - -25 - - - - 21 - 2 - (:auto !!!:) (:include synopsis:) !!!!Requirements: T must be a class with an accessible no-throw copy constructor. !!!!Returns: An object of ''unspecified'' type which derives publicly from T. That is, the returned object can be intercepted by a catch(T &). !!!!Description: This function is designed to be used directly in a throw-expression to enable the (:link - 1 - - 0 - - -22 - - - 2 - :) support in Boost Exception. For example: [@class my_exception: public std::exception { }; .... throw boost::(:link - 1 - - 0 - - -25 - - - 2 - :)(my_exception());@] Unless (:link - 1 - - 0 - - -25 - - - 2 - :) is called at the time an exception object is used in a throw-expression, an attempt to copy it using (:link - 1 - - 0 - - -8 - - - 2 - :) may return an (:link - 1 - - 0 - - -22 - - - 2 - :) which refers to an instance of (:link - 1 - - 0 - - -35 - - - 2 - :). See (:link - 1 - - 0 - - -8 - - - 2 - :) for details. !!!!Note: Instead of using the throw keyword directly, it is preferable to call boost::(:link - 1 - - 0 - - -39 - - - 2 - :). This is guaranteed to throw an exception that derives from boost::(:link - 1 - - 0 - - -42 - - - 2 - :) and supports the (:link - 1 - - 0 - - -22 - - - 2 - :) functionality. - - - - - 0 - - -26 + -27 @@ -7065,7 +7078,7 @@ 0 - -39 + -40 2 @@ -7074,7 +7087,7 @@ 0 - -36 + -37 2 @@ -7083,26 +7096,13 @@ 0 - -6 + -5 2 . - - - 0 - - -27 - - - - 1 - 2 - (:auto !!!:) !!!Synopsis (:include synopsis:) - - 0 @@ -7118,7 +7118,7 @@ 0 - -42 + -43 2 @@ -7127,7 +7127,7 @@ 0 - -6 + -5 2 @@ -7159,179 +7159,6 @@ -29 - - 19 - 2 - (:auto !!!:) Sometimes the throw site does not have all the information that is needed at the catch site to make sense of what went wrong. Let's say we have an exception type file_read_error, which takes a file name in its constructor. Consider the following function: [@void file_read( FILE * f, void * buffer, size_t size ) { if( size!=fread(buffer,1,size,f) ) throw file_read_error(????); }@] How can the file_read function pass a file name to the exception type constructor? All it has is a FILE handle. Using boost::(:link - 1 - - 0 - - -42 - - - 2 - :) allows us to free the file_read function from the burden of storing the file name in exceptions it throws: [@#include <(:link - 1 - - 0 - - -50 - - - 2 - :)> #include <stdio.h> #include <errno.h> typedef boost::(:link - 1 - - 0 - - -43 - - - 2 - :)<struct tag_errno,int> errno_info; class file_read_error: public boost::(:link - 1 - - 0 - - -42 - - - 2 - :) { }; void file_read( FILE * f, void * buffer, size_t size ) { if( size!=fread(buffer,1,size,f) ) throw file_read_error() << errno_info(errno); }@] If file_read detects a failure, it throws an exception which contains the information that is available at the time, namely the errno. Other relevant information, such as the file name, can be added in a context higher up the call stack, where it is known naturally: [@#include <(:link - 1 - - 0 - - -50 - - - 2 - :)> #include <boost/shared_ptr.hpp> #include <stdio.h> #include <string> typedef boost::(:link - 1 - - 0 - - -43 - - - 2 - :)<struct tag_file_name,std::string> file_name_info; boost::shared_ptr<FILE> file_open( char const * file_name, char const * mode ); void file_read( FILE * f, void * buffer, size_t size ); void parse_file( char const * file_name ) { boost::shared_ptr<FILE> f = file_open(file_name,"rb"); assert(f); try { char buf[1024]; file_read( f.get(), buf, sizeof(buf) ); } catch( boost::(:link - 1 - - 0 - - -42 - - - 2 - :) & e ) { e << file_name_info(file_name); throw; } }@] The above function is (almost) exception-neutral -- if an exception is emitted by any function call within the try block, parse_file does not need to do any real work, but it intercepts any boost::(:link - 1 - - 0 - - -42 - - - 2 - :) object, stores the file name, and re-throws using a throw-expression with no operand (15.1.6). The rationale for catching any boost::(:link - 1 - - 0 - - -42 - - - 2 - :) object is that the file name is relevant to any failure that occurs in parse_file, ''even if the failure is unrelated to file I/O''. - - - - - 0 - - -30 - - - - 1 - 2 - (:auto !!!:) (:include synopsis:) !!!!Requirements: This function must not be called outside of a catch block. !!!!Returns: A pointer of type E to the current exception object, or null if the current exception object can not be converted to E *. !!!!Throws: Nothing. - - - - - 0 - - -31 - - - - 5 - 2 - (:auto !!!:) (:include synopsis:) !!!!Description: Returns a const reference to the copy of the value passed to (:link - 1 - - 0 - - -43 - - - 2 - :)'s constructor stored in the (:link - 1 - - 0 - - -43 - - - 2 - :) object. !!!!Throws: Nothing. - - - - - 0 - - -32 - - - - 1 - 2 - (:auto !!:) !!!Synopsis (:include synopsis:) - - - - - 0 - - -33 - - - - 3 - 2 - !!!!Example: this is a possible output from the (:link - 1 - - 0 - - -6 - - - 2 - :) function, as used in ''libs/exception/example/example_io.cpp:'' [@example_io.cpp(83): Throw in function class boost::shared_ptr<struct _iobuf> __cdecl my_fopen(const char *,const char *) Dynamic exception type: class boost::exception_detail::clone_impl<class fopen_error> std::exception::what: example_io error [struct tag_errno *] = 2, OS says "No such file or directory" [struct tag_file_name *] = tmp1.txt [struct tag_function *] = fopen [struct tag_open_mode *] = rb@] - - - - - 0 - - -34 - - 45 2 @@ -7340,7 +7167,7 @@ 0 - -12 + -14 2 @@ -7349,7 +7176,7 @@ 0 - -12 + -14 2 @@ -7430,7 +7257,7 @@ 0 - -32 + -33 2 @@ -7439,7 +7266,7 @@ 0 - -32 + -33 2 @@ -7484,7 +7311,7 @@ 0 - -27 + -19 2 @@ -7493,7 +7320,7 @@ 0 - -27 + -19 2 @@ -7540,31 +7367,186 @@ 0 - -35 + -30 + + + + 19 + 2 + (:auto !!!:) Sometimes the throw site does not have all the information that is needed at the catch site to make sense of what went wrong. Let's say we have an exception type file_read_error, which takes a file name in its constructor. Consider the following function: [@void file_read( FILE * f, void * buffer, size_t size ) { if( size!=fread(buffer,1,size,f) ) throw file_read_error(????); }@] How can the file_read function pass a file name to the exception type constructor? All it has is a FILE handle. Using boost::(:link + 1 + + 0 + + -43 + + + 2 + :) allows us to free the file_read function from the burden of storing the file name in exceptions it throws: [@#include <(:link + 1 + + 0 + + -50 + + + 2 + :)> #include <stdio.h> #include <errno.h> typedef boost::(:link + 1 + + 0 + + -44 + + + 2 + :)<struct tag_errno,int> errno_info; class file_read_error: public boost::(:link + 1 + + 0 + + -43 + + + 2 + :) { }; void file_read( FILE * f, void * buffer, size_t size ) { if( size!=fread(buffer,1,size,f) ) throw file_read_error() << errno_info(errno); }@] If file_read detects a failure, it throws an exception which contains the information that is available at the time, namely the errno. Other relevant information, such as the file name, can be added in a context higher up the call stack, where it is known naturally: [@#include <(:link + 1 + + 0 + + -50 + + + 2 + :)> #include <boost/shared_ptr.hpp> #include <stdio.h> #include <string> typedef boost::(:link + 1 + + 0 + + -44 + + + 2 + :)<struct tag_file_name,std::string> file_name_info; boost::shared_ptr<FILE> file_open( char const * file_name, char const * mode ); void file_read( FILE * f, void * buffer, size_t size ); void parse_file( char const * file_name ) { boost::shared_ptr<FILE> f = file_open(file_name,"rb"); assert(f); try { char buf[1024]; file_read( f.get(), buf, sizeof(buf) ); } catch( boost::(:link + 1 + + 0 + + -43 + + + 2 + :) & e ) { e << file_name_info(file_name); throw; } }@] The above function is (almost) exception-neutral -- if an exception is emitted by any function call within the try block, parse_file does not need to do any real work, but it intercepts any boost::(:link + 1 + + 0 + + -43 + + + 2 + :) object, stores the file name, and re-throws using a throw-expression with no operand (15.1.6). The rationale for catching any boost::(:link + 1 + + 0 + + -43 + + + 2 + :) object is that the file name is relevant to any failure that occurs in parse_file, ''even if the failure is unrelated to file I/O''. + + + + + 0 + + -31 + + + + 1 + 2 + (:auto !!!:) (:include synopsis:) !!!!Requirements: This function must not be called outside of a catch block. !!!!Returns: A pointer of type E to the current exception object, or null if the current exception object can not be converted to E *. !!!!Throws: Nothing. + + + + + 0 + + -32 5 2 - (:auto !!!:) (:include synopsis:) This type is used by the (:link + (:auto !!!:) (:include synopsis:) !!!!Description: Returns a const reference to the copy of the value passed to (:link 1 0 - -22 + -44 2 - :) support in Boost Exception. Please see (:link + :)'s constructor stored in the (:link 1 0 - -8 + -44 2 - :). + :) object. !!!!Throws: Nothing. + + + + + 0 + + -33 + + + + 1 + 2 + (:auto !!:) !!!Synopsis (:include synopsis:) + + + + + 0 + + -34 + + + + 3 + 2 + !!!!Example: this is a possible output from the (:link + 1 + + 0 + + -5 + + + 2 + :) function, as used in ''libs/exception/example/example_io.cpp:'' [@example_io.cpp(83): Throw in function class boost::shared_ptr<struct _iobuf> __cdecl my_fopen(const char *,const char *) Dynamic exception type: class boost::exception_detail::clone_impl<class fopen_error> std::exception::what: example_io error [struct tag_errno *] = 2, OS says "No such file or directory" [struct tag_file_name *] = tmp1.txt [struct tag_function *] = fopen [struct tag_open_mode *] = rb@] + + + + + 0 + + -35 + + + + 1 + 2 + (:auto !!:) (:pagelist fmt="index" tags="function":) @@ -7575,59 +7557,23 @@ - 13 + 5 2 - (:auto !!!:) (:include synopsis:) !!!!Requirements: * ErrorInfo must be an instance of the (:link + (:auto !!!:) (:include synopsis:) This type is used by the (:link 1 0 - -43 + -24 2 - :) template. * E must be polymorphic. !!!!Returns: * If dynamic_cast<boost::(:link + :) support in Boost Exception. Please see (:link 1 0 - -42 - - - 2 - :) const *>(&x) is 0, or if x does not store an object of type ErrorInfo, the returned value is null. * Otherwise, the returned pointer points to the stored value (use (:link - 1 - - 0 - - -17 - - - 2 - mod="/":) to store values in exception objects.) When x is destroyed, any pointers returned by (:link - 1 - - 0 - - -36 - - - 2 - :) become invalid. !!!!Throws: Nothing. !!!!Note: The interface of (:link - 1 - - 0 - - -36 - - - 2 - :) may be affected by the build (:link - 1 - - 0 - - -5 + -6 2 @@ -7642,117 +7588,18 @@ - 69 + 13 2 - !!Introduction The purpose of Boost Exception is to ease the design of exception class hierarchies and to help write exception handling and error reporting code. It supports transporting of arbitrary data to the catch site, which is otherwise tricky due to the no-throw requirements (15.5.1) for exception types. Data can be added to any exception object, either directly in the throw-expression (15.1), or at a later time as the exception object propagates up the call stack. The ability to add data to exception objects after they have been passed to throw is important, because often some of the information needed to handle an exception is unavailable in the context where the failure is detected. Boost Exception also supports (:link http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2179.html|N2179:)-style (:link + (:auto !!!:) (:include synopsis:) !!!!Requirements: * ErrorInfo must be an instance of the (:link 1 0 - -38 + -44 2 - |copying:) of exception objects, implemented non-intrusively and automatically by the boost::(:link - 1 - - 0 - - -39 - - - 2 - :) function. !!Contents #(:link - 1 - - 0 - - -18 - - - 2 - :) #Tutorial ##(:link - 1 - - 0 - - -11 - - - 2 - mod="w":) ##(:link - 1 - - 0 - - -20 - - - 2 - mod="w":) ##(:link - 1 - - 0 - - -38 - - - 2 - mod="w":) ##(:link - 1 - - 0 - - -19 - - - 2 - mod="w":) ##(:link - 1 - - 0 - - -41 - - - 2 - mod="w":) ##(:link - 1 - - 0 - - -14 - - - 2 - mod="w":) #Documentation ##Class (:link - 1 - - 0 - - -42 - - - 2 - :) ##Throwing Exceptions ###(:link - 1 - - 0 - - -26 - - - 2 - :) ###(:link - 1 - - 0 - - -39 - - - 2 - :) ##Transporting of Arbitrary Data to the Catch Site ###(:link + :) template. * E must be polymorphic. !!!!Returns: * If dynamic_cast<boost::(:link 1 0 @@ -7761,43 +7608,92 @@ 2 - :) ###(:link + :) const *>(&x) is 0, or if x does not store an object of type ErrorInfo, the returned value is null. * Otherwise, the returned pointer points to the stored value (use (:link 1 0 - -17 + -18 2 - :) ###(:link + mod="/":) to store values in exception objects.) When x is destroyed, any pointers returned by (:link 1 0 - -10 + -37 2 - :) ###(:link + :) become invalid. !!!!Throws: Nothing. !!!!Note: The interface of (:link 1 0 - -36 + -37 2 - :) ###(:link + :) may be affected by the build (:link 1 0 - -21 + -7 2 - :) ##(:link http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2179.html|N2179:) Transporting of Exceptions between Threads ###(:link + :). + + + + + 0 + + -38 + + + + 69 + 2 + !!Introduction The purpose of Boost Exception is to ease the design of exception class hierarchies and to help write exception handling and error reporting code. It supports transporting of arbitrary data to the catch site, which is otherwise tricky due to the no-throw requirements (15.5.1) for exception types. Data can be added to any exception object, either directly in the throw-expression (15.1), or at a later time as the exception object propagates up the call stack. The ability to add data to exception objects after they have been passed to throw is important, because often some of the information needed to handle an exception is unavailable in the context where the failure is detected. Boost Exception also supports (:link http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2179.html|N2179:)-style (:link + 1 + + 0 + + -39 + + + 2 + |copying:) of exception objects, implemented non-intrusively and automatically by the boost::(:link + 1 + + 0 + + -40 + + + 2 + :) function. !!Contents #(:link + 1 + + 0 + + -20 + + + 2 + :) #Tutorial ##(:link + 1 + + 0 + + -13 + + + 2 + mod="w":) ##(:link 1 0 @@ -7806,12 +7702,120 @@ 2 + mod="w":) ##(:link + 1 + + 0 + + -39 + + + 2 + mod="w":) ##(:link + 1 + + 0 + + -21 + + + 2 + mod="w":) ##(:link + 1 + + 0 + + -42 + + + 2 + mod="w":) ##(:link + 1 + + 0 + + -10 + + + 2 + mod="w":) #Documentation ##Class (:link + 1 + + 0 + + -43 + + + 2 + :) ##Throwing Exceptions ###(:link + 1 + + 0 + + -27 + + + 2 :) ###(:link 1 0 - -25 + -40 + + + 2 + :) ##Transporting of Arbitrary Data to the Catch Site ###(:link + 1 + + 0 + + -44 + + + 2 + :) ###(:link + 1 + + 0 + + -18 + + + 2 + :) ###(:link + 1 + + 0 + + -12 + + + 2 + :) ###(:link + 1 + + 0 + + -37 + + + 2 + :) ###(:link + 1 + + 0 + + -23 + + + 2 + :) ##(:link http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2179.html|N2179:) Transporting of Exceptions between Threads ###(:link + 1 + + 0 + + -24 2 @@ -7829,7 +7833,7 @@ 0 - -13 + -6 2 @@ -7838,7 +7842,7 @@ 0 - -40 + -15 2 @@ -7847,7 +7851,16 @@ 0 - -35 + -41 + + + 2 + :) ###(:link + 1 + + 0 + + -36 2 @@ -7856,7 +7869,7 @@ 0 - -6 + -5 2 @@ -7874,7 +7887,7 @@ 0 - -30 + -31 2 @@ -7883,7 +7896,7 @@ 0 - -34 + -29 2 @@ -7901,7 +7914,7 @@ 0 - -46 + -47 2 @@ -7910,7 +7923,7 @@ 0 - -48 + -35 2 @@ -7928,7 +7941,7 @@ 0 - -5 + -7 2 @@ -7937,7 +7950,7 @@ 0 - -16 + -17 2 @@ -7957,7 +7970,7 @@ 0 - -38 + -39 @@ -7968,7 +7981,7 @@ 0 - -25 + -8 2 @@ -7977,7 +7990,7 @@ 0 - -39 + -40 2 @@ -7986,7 +7999,7 @@ 0 - -42 + -43 2 @@ -7995,7 +8008,7 @@ 0 - -47 + -48 2 @@ -8004,7 +8017,7 @@ 0 - -7 + -9 2 @@ -8015,7 +8028,7 @@ 0 - -39 + -40 @@ -8026,7 +8039,7 @@ 0 - -39 + -40 2 @@ -8035,7 +8048,7 @@ 0 - -25 + -8 2 @@ -8044,7 +8057,7 @@ 0 - -21 + -23 2 @@ -8053,7 +8066,7 @@ 0 - -39 + -40 2 @@ -8062,7 +8075,7 @@ 0 - -39 + -40 2 @@ -8071,7 +8084,7 @@ 0 - -39 + -40 2 @@ -8080,7 +8093,7 @@ 0 - -36 + -37 2 @@ -8089,7 +8102,7 @@ 0 - -6 + -5 2 @@ -8100,7 +8113,7 @@ 0 - -40 + -41 @@ -8113,7 +8126,7 @@ 0 - -41 + -42 @@ -8124,7 +8137,7 @@ 0 - -42 + -43 2 @@ -8133,7 +8146,7 @@ 0 - -19 + -21 2 @@ -8144,7 +8157,7 @@ 0 - -42 + -43 @@ -8155,7 +8168,7 @@ 0 - -42 + -43 2 @@ -8164,7 +8177,7 @@ 0 - -42 + -43 2 @@ -8173,7 +8186,7 @@ 0 - -43 + -44 2 @@ -8182,7 +8195,7 @@ 0 - -17 + -18 2 @@ -8191,7 +8204,7 @@ 0 - -42 + -43 2 @@ -8200,7 +8213,7 @@ 0 - -36 + -37 2 @@ -8211,7 +8224,7 @@ 0 - -43 + -44 @@ -8222,7 +8235,7 @@ 0 - -43 + -44 2 @@ -8231,7 +8244,7 @@ 0 - -17 + -18 2 @@ -8240,7 +8253,7 @@ 0 - -42 + -43 2 @@ -8258,7 +8271,7 @@ 0 - -43 + -44 2 @@ -8276,7 +8289,7 @@ 0 - -43 + -44 2 @@ -8294,7 +8307,7 @@ 0 - -43 + -44 2 @@ -8303,7 +8316,7 @@ 0 - -17 + -18 2 @@ -8321,7 +8334,7 @@ 0 - -42 + -43 2 @@ -8330,34 +8343,34 @@ 0 - -17 + -18 2 - |<<:) errno_info(errno);@] It can also be passed to + |<<:) errno_info(errno);@] It can also be passed to (:link 1 0 - -36 + -37 2 - (#include < + :) (#include <(:link 1 0 - -15 + -16 2 - > first) to retrieve the tag_errno int from a boost::(:link + :)> first) to retrieve the tag_errno int from a boost::(:link 1 0 - -42 + -43 2 @@ -8366,27 +8379,27 @@ 0 - -42 + -43 2 - :) & x ) { if( boost::shared_ptr<int const> e=boost:: + :) & x ) { if( int const * e=boost::(:link 1 0 - -36 + -37 2 - <errno_info>(x) ) .... }@] + :)<errno_info>(x) ) .... }@] 0 - -44 + -45 @@ -8397,7 +8410,7 @@ 0 - -42 + -43 2 @@ -8406,7 +8419,7 @@ 0 - -42 + -43 2 @@ -8415,7 +8428,7 @@ 0 - -17 + -18 2 @@ -8426,7 +8439,7 @@ 0 - -45 + -46 @@ -8446,7 +8459,7 @@ 0 - -43 + -44 2 @@ -8455,7 +8468,7 @@ 0 - -42 + -43 2 @@ -8464,7 +8477,7 @@ 0 - -43 + -44 2 @@ -8473,7 +8486,7 @@ 0 - -42 + -43 2 @@ -8482,7 +8495,7 @@ 0 - -17 + -18 2 @@ -8491,7 +8504,7 @@ 0 - -36 + -37 2 @@ -8500,7 +8513,7 @@ 0 - -36 + -37 2 @@ -8511,7 +8524,7 @@ 0 - -46 + -47 @@ -8524,7 +8537,7 @@ 0 - -47 + -48 @@ -8544,7 +8557,7 @@ 0 - -42 + -43 2 @@ -8553,7 +8566,7 @@ 0 - -25 + -8 2 @@ -8562,7 +8575,7 @@ 0 - -25 + -8 2 @@ -8571,26 +8584,13 @@ 0 - -42 + -43 2 :). - - - 0 - - -48 - - - - 1 - 2 - (:auto !!:) (:pagelist fmt="index" tags="function":) - - 0 @@ -8632,7 +8632,7 @@ 0 - -43 + -44 2 @@ -8831,9 +8831,7 @@ - 1 - 2 - !!!!Throws: Any exception emitted by v's copy constructor. + 0 @@ -8844,9 +8842,7 @@ - 1 - 2 - !!!!Throws: std::bad_alloc, or any exception emitted by T1..TN copy constructor. + 0 @@ -8857,7 +8853,9 @@ - 0 + 1 + 2 + !!!!Throws: Any exception emitted by v's copy constructor. @@ -8868,7 +8866,9 @@ - 0 + 1 + 2 + !!!!Throws: std::bad_alloc, or any exception emitted by T1..TN copy constructor. @@ -8923,9 +8923,7 @@ - 1 - 2 - !!!!Throws: std::bad_alloc, or any exception emitted by the T copy constructor. + 0 @@ -8936,7 +8934,9 @@ - 0 + 1 + 2 + !!!!Throws: std::bad_alloc, or any exception emitted by the T copy constructor. @@ -9423,7 +9423,18 @@ - 0 + 3 + 2 + `#include <(:link + 1 + + 0 + + -33 + + + 2 + :)>\\ [@namespace boost { (:include decl pre_indent="4":) }@] @@ -9441,11 +9452,11 @@ 0 - -32 + -57 2 - :)>\\ [@namespace boost { (:include decl pre_indent="4":) }@] + :)> [@namespace boost { (:include decl pre_indent="4":) }@] @@ -9469,16 +9480,16 @@ 3 2 - `#include <(:link + `#include < 1 0 - -57 + -19 2 - :)> [@namespace boost { (:include decl pre_indent="4":) }@] + > [@namespace boost { (:include decl pre_indent="4":) }@] @@ -9488,6 +9499,28 @@ -9 + + 0 + + + + + 0 + + -10 + + + + 0 + + + + + 0 + + -11 + + 3 2 @@ -9507,7 +9540,7 @@ 0 - -10 + -12 @@ -9527,7 +9560,7 @@ 0 - -10 + -12 2 @@ -9538,7 +9571,7 @@ 0 - -11 + -13 @@ -9549,7 +9582,7 @@ 0 - -12 + -14 @@ -9562,7 +9595,7 @@ 0 - -13 + -15 @@ -9584,18 +9617,7 @@ 0 - -14 - - - - 0 - - - - - 0 - - -15 + -16 @@ -9608,7 +9630,7 @@ 0 - -16 + -17 @@ -9619,7 +9641,7 @@ 0 - -17 + -18 @@ -9637,17 +9659,6 @@ :)>\\ [@namespace boost { (:include decl pre_indent="4":) }@] - - - 0 - - -18 - - - - 0 - - 0 @@ -9656,7 +9667,18 @@ - 0 + 3 + 2 + [@#include < + 1 + + 0 + + -14 + + + 2 + > namespace boost { (:include api pre_indent="4":) }@] @@ -9677,6 +9699,28 @@ -21 + + 0 + + + + + 0 + + -22 + + + + 0 + + + + + 0 + + -23 + + 3 2 @@ -9696,7 +9740,7 @@ 0 - -22 + -24 @@ -9714,28 +9758,6 @@ :)> [@namespace boost { (:include decl pre_indent="4":) }@] - - - 0 - - -23 - - - - 0 - - - - - 0 - - -24 - - - - 0 - - 0 @@ -9744,18 +9766,7 @@ - 3 - 2 - `#include < - 1 - - 0 - - -27 - - - 2 - > [@namespace boost { (:include decl pre_indent="4":) }@] + 0 @@ -9765,6 +9776,17 @@ -26 + + 0 + + + + + 0 + + -27 + + 3 2 @@ -9780,28 +9802,6 @@ > (:include decl:) - - - 0 - - -27 - - - - 3 - 2 - [@#include < - 1 - - 0 - - -12 - - - 2 - > namespace boost { (:include api pre_indent="4":) }@] - - 0 @@ -9817,7 +9817,7 @@ 0 - -32 + -33 2 @@ -9842,6 +9842,17 @@ -30 + + 0 + + + + + 0 + + -31 + + 3 2 @@ -9861,7 +9872,7 @@ 0 - -31 + -32 @@ -9883,7 +9894,7 @@ 0 - -32 + -33 @@ -9894,24 +9905,13 @@ 0 - -42 + -43 2 decl pre_indent="4":) (:include api pre_indent="4":) }@] - - - 0 - - -33 - - - - 0 - - 0 @@ -9930,6 +9930,17 @@ -35 + + 0 + + + + + 0 + + -36 + + 3 2 @@ -9949,7 +9960,7 @@ 0 - -36 + -37 @@ -9958,17 +9969,6 @@ [@namespace boost { (:include decl pre_indent="4":) }@] - - - 0 - - -37 - - - - 0 - - 0 @@ -9987,6 +9987,17 @@ -39 + + 0 + + + + + 0 + + -40 + + 3 2 @@ -10006,7 +10017,7 @@ 0 - -40 + -41 @@ -10024,17 +10035,6 @@ :)> [@namespace boost { (:include decl pre_indent="4":) }@] - - - 0 - - -41 - - - - 0 - - 0 @@ -10043,18 +10043,7 @@ - 3 - 2 - `#include <(:link - 1 - - 0 - - -12 - - - 2 - :)> [@namespace boost { (:include def pre_indent="4":) }@] + 0 @@ -10072,7 +10061,7 @@ 0 - -56 + -14 2 @@ -10087,7 +10076,18 @@ - 0 + 3 + 2 + `#include <(:link + 1 + + 0 + + -56 + + + 2 + :)> [@namespace boost { (:include def pre_indent="4":) }@] @@ -10206,7 +10206,7 @@ 0 - -12 + -14 2 @@ -10263,7 +10263,7 @@ 0 - -12 + -14 2 @@ -10285,7 +10285,7 @@ 0 - -12 + -14 2 @@ -10520,23 +10520,6 @@ 56 - - - - - 0 - - - - - - 1 - - - - -37 - - @@ -10568,7 +10551,24 @@ - -11 + -39 + + + + + + + 0 + + + + + + 1 + + + + -13 @@ -10605,57 +10605,6 @@ -52 - - - - - 0 - - - - - - 1 - - - - -27 - - - - - - - 0 - - - - - - 1 - - - - -18 - - - - - - - 0 - - - - - - 1 - - - - -41 - - @@ -10687,7 +10636,7 @@ - -16 + -20 @@ -10704,7 +10653,58 @@ - -48 + -42 + + + + + + + 0 + + + + + + 1 + + + + -21 + + + + + + + 0 + + + + + + 1 + + + + -17 + + + + + + + 0 + + + + + + 1 + + + + -35 @@ -10738,7 +10738,7 @@ - -46 + -47 @@ -10772,7 +10772,7 @@ - -34 + -29 @@ -10796,7 +10796,7 @@ - -7 + -9 @@ -10820,7 +10820,7 @@ - -33 + -34 @@ -10844,7 +10844,7 @@ - -20 + -22 @@ -10872,7 +10872,7 @@ - -30 + -31 @@ -10900,7 +10900,7 @@ - -35 + -36 @@ -10928,7 +10928,7 @@ - -8 + -6 @@ -10956,7 +10956,7 @@ - -22 + -24 @@ -10984,7 +10984,7 @@ - -40 + -41 @@ -11012,7 +11012,7 @@ - -13 + -15 @@ -11040,7 +11040,7 @@ - -36 + -37 @@ -11064,7 +11064,7 @@ - -14 + -10 @@ -11116,7 +11116,7 @@ - -9 + -11 @@ -11144,7 +11144,7 @@ - -17 + -18 @@ -11168,7 +11168,7 @@ - -45 + -46 @@ -11244,7 +11244,7 @@ - -39 + -40 @@ -11276,7 +11276,7 @@ - -5 + -7 @@ -11328,7 +11328,7 @@ - -43 + -44 @@ -11392,7 +11392,7 @@ - -31 + -32 @@ -11416,7 +11416,7 @@ - -15 + -16 @@ -11444,7 +11444,7 @@ - -6 + -5 @@ -11520,7 +11520,7 @@ - -12 + -14 @@ -11548,7 +11548,7 @@ - -23 + -25 @@ -11576,7 +11576,7 @@ - -25 + -8 @@ -11604,7 +11604,7 @@ - -21 + -23 @@ -11632,7 +11632,7 @@ - -42 + -43 @@ -11664,7 +11664,7 @@ - -44 + -45 @@ -11712,7 +11712,7 @@ - -47 + -48 @@ -11736,7 +11736,7 @@ - -26 + -27 @@ -11760,7 +11760,7 @@ - -29 + -30 @@ -11784,7 +11784,7 @@ - -32 + -33 @@ -11840,7 +11840,7 @@ - -10 + -12 @@ -11864,7 +11864,7 @@ - -24 + -26 @@ -11892,7 +11892,7 @@ 0 - -6 + -5 diagnostic_information free function @@ -11901,10 +11901,10 @@ 0 - -7 + -6 - noindex tutorial + exception_ptr free function @@ -11922,7 +11922,7 @@ -9 - function member + noindex tutorial @@ -11931,7 +11931,7 @@ -10 - error_info free function + diagnostic_information tutorial @@ -11940,7 +11940,7 @@ -11 - tutorial + function member @@ -11949,7 +11949,7 @@ -12 - + error_info free function @@ -11958,7 +11958,7 @@ -13 - exception_ptr free function + tutorial @@ -11967,7 +11967,7 @@ -14 - diagnostic_information tutorial + @@ -11976,13 +11976,22 @@ -15 + exception_ptr free function + + + + 0 + + -16 + + error_info 0 - -17 + -18 error_info free function @@ -11991,19 +12000,10 @@ 0 - -20 + -19 - tutorial - - - - 0 - - -21 - - - error_info free function + exception_ptr @@ -12012,7 +12012,7 @@ -22 - type + tutorial @@ -12021,7 +12021,7 @@ -23 - function + error_info free function @@ -12030,7 +12030,7 @@ -24 - noalso noindex tutorial + type @@ -12039,7 +12039,7 @@ -25 - exception_ptr free function + function @@ -12048,7 +12048,7 @@ -26 - macro + noalso noindex tutorial @@ -12057,7 +12057,7 @@ -27 - exception_ptr + macro @@ -12072,7 +12072,7 @@ 0 - -29 + -30 noalso noindex tutorial @@ -12081,7 +12081,7 @@ 0 - -30 + -31 function @@ -12090,7 +12090,7 @@ 0 - -31 + -32 function member @@ -12099,7 +12099,7 @@ 0 - -32 + -33 @@ -12108,7 +12108,7 @@ 0 - -35 + -36 exception_ptr type @@ -12117,7 +12117,7 @@ 0 - -36 + -37 error_info free function @@ -12126,20 +12126,11 @@ 0 - -37 + -38 noindex - - - 0 - - -38 - - - tutorial - 0 @@ -12147,7 +12138,7 @@ -39 - free function + tutorial @@ -12156,7 +12147,7 @@ -40 - exception_ptr free function + free function @@ -12165,7 +12156,7 @@ -41 - tutorial + exception_ptr free function @@ -12174,7 +12165,7 @@ -42 - type + tutorial @@ -12192,7 +12183,7 @@ -44 - function + type @@ -12201,13 +12192,22 @@ -45 + function + + + + 0 + + -46 + + noalso noindex tutorial 0 - -47 + -48 noindex tutorial