Project

General

Profile

Bug #872

catch(...) should be treated like if (...) in style guide

Added by Rogers, Chris over 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
Testing
Target version:
Start date:
20 January 2012
Due date:
% Done:

100%

Estimated time:
Workflow:
New Issue

Description

so should have a space before brackets...

#1

Updated by Lane, Peter over 8 years ago

  • Assignee changed from Rogers, Chris to Lane, Peter

I got tired of adding style exceptions for all my code, so I hacked cpplint.py to treat 'catch' like the other control statements (if, for, switch, etc...). Yes, I could have just conformed to all the other code, but I'm obsessive compulsive sometimes. Is it my fault Google doesn't use C++ exceptions and didn't bother with 'catch' statments?

At any rate, I also used a script to change all the now non-conforming statements. Sorry, this is going to affect a lot of files just like the Squeal -> MAUS::Exception changes.

#2

Updated by Lane, Peter over 8 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Modifications to cpplint.py and files to conform in lp:maus/merge.

#3

Updated by Rajaram, Durga over 8 years ago

  • Target version changed from Future MAUS release to MAUS-v0.8.0

Also available in: Atom PDF