indent bug? at least strange

[chris lueders]

hi,

i'm delighted to see that indent is still there and it helps me to
make unreadable MS samples readable to me :)

there is one thing, though, that i wonder if it's intentional.  if i
have this source:

void foo() {
   a(b[0]
       );
}

and process it with "indent -bl <x.cpp" i get this (expected) result:

void
foo ()
{
  a (b[0]);
}

but if i use "indent -br <x.cpp" it keeps the broken off parenthesis
for the function call:

void
foo ()
{
  a (b[0]
    );
}

-br is part of --k-and-r-style, which i would like to use.  it works
ok if the source is like this (no subscript):

void foo() {
   a(b
   );
}

and the problem only shows if the parenthesis is broken off to begin with.

bug or no bug, is there any way i can force indent to unbreak the
closing parenthesis with -br?

thanks for your great work!

-- 
/chris/

* http://www.cfos.de -- High Speed & Low Ping through Traffic Shaping
* cFosSpeed 7.00 -- download: http://www.cfos.de/download
*
* cFos Software GmbH, Bonn - eingetragen beim Amtsgericht Bonn,
* HRB 9150 - Geschaeftsfuehrer: Christoph Lueders & Martin Winkler