wlue on What was the strangest coding standard rule that you were forced to follow?

Comment on What was the strangest coding standard rule that you were forced to follow?

I worked at a start-up whose engineering lead brought familiar coding style to a project that was inherited. We were imposed a combination of C89-esque and Microsoft kernel coding style on an Objective-C source code. Things like defining all variables at the beginning of the function definition in alphabetical order in CamelCase, having instance variables prefixed with the class abbreviation, and other inane rules. It went something like this:

  - (void)
  doSomethingOnObjectAndNumber:
    (NSObject *) MyObject :
    (NSInteger) MyNumber
  
  /*++
  Some unstandard doc format.
  --*/

  {
    
    ...
    return;
  }

Before I started, I was told that the project migrated from git to svn to "make branching easier". I do not work there any more.

Comments