fix try/catch

From-SVN: r33861
This commit is contained in:
Jason Merrill 2000-05-11 16:11:09 -04:00
parent 48a259fc43
commit efe7ef89e9

View File

@ -107,14 +107,20 @@ Notable areas of divergence from what may be previous local practice
{ } { }
08. Try/Catch blocks 08. Try/Catch blocks
try { try
// {
} //
catch(...) { }
// catch (...)
} {
//
}
-NOT- -NOT-
try { // } catch(...) { // } try {
//
} catch(...) {
//
}
09. Member functions declarations and defintions 09. Member functions declarations and defintions
Keywords such as extern, static, export, explicit, inline, etc Keywords such as extern, static, export, explicit, inline, etc
@ -128,7 +134,7 @@ Notable areas of divergence from what may be previous local practice
Reason: GNU coding conventions dictate return types for functions Reason: GNU coding conventions dictate return types for functions
are on a separate line than the function name and parameter list are on a separate line than the function name and parameter list
for definitions. For C++, where we have member functions that can for definitions. For C++, where we have member functions that can
. be either inline definitions or declarations, keeping to this be either inline definitions or declarations, keeping to this
standard allows all member function names for a given class to be standard allows all member function names for a given class to be
aligned to the same margin, increasing readibility. aligned to the same margin, increasing readibility.
@ -140,6 +146,8 @@ Notable areas of divergence from what may be previous local practice
-NOT- -NOT-
sync() sync()
Reason: ???
The library currently has a mixture of GNU-C and modern C++ coding The library currently has a mixture of GNU-C and modern C++ coding
styles. The GNU C usages will be combed out gradually. styles. The GNU C usages will be combed out gradually.