Foo Bar

It's really great that there are so many tests available! But it seems that some of them are not working with official version 3.1, are they? [ PASSED ] 2698 tests. [ FAILED ] 11 tests, listed below: [ FAILED ] BugFix_V32.ObjCAutoReleasePool [ FAILED ] BugFix_V32.ObjCTypeVariable [ FAILED ] ObjCStyleF.WebKit [ FAILED ] StyleWebKitCppF.LongOption [ FAILED ] StyleWebKitCppF.Short [ FAILED ] StyleWebKitCpp.SpaceIndent [ FAILED ] StyleWebKitCpp.Tab [ FAILED ] StyleWebKitCpp.TabIndent [ FAILED ] StyleWebKitCpp.ForceTab...

It's really great that there are so many tests available! But it seems that some of them are not working with official version 3.1, are they?

In my opinion it's exactly vice versa, the blank after int * is fine whereas there is one missing after float *. My patch for #501 will also fix this one. If you don't like any spaces being added before or after the asterisk you shouldn't use option --align-pointer at all, should you?

In my opinion it's exactly vice versa, the blank after "int *" is fine whereas there is one missing after float. My patch for #501 will also fix this one. If you don't like any spaces being added before or after the asterisk you shouldn't use option --align-pointer at all, should you?

In my opinion it's exactly vice versa, the blank after int is fine whereas there is one missing after float. My patch for #501 will also fix this one. If you don't like any spaces being added before or after the asterisk you shouldn't use option --align-pointer at all, should you?

Nearly all types (exept char, int, void, xxx_t, INT and VOID) are affected by this, even self defined types. The attached patch (#501.patch) is probably the most minimally invasive change that would fix all of them. But on the other side will damage "--align-pointer" for self defined types only. It's not absolutely clear for me what function isPointerOrReferenceVariable should really do, so maybe attached patch (#501_more_universal.patch) would do a better job, especially since function isNumericVariable...

Can be reproduced on windows, too. I think there is something wrong around line 1479. The attached patch fixes the problem but I'm not sure about any side effects. Maybe Jim Pattee find some time to have a short look at it? Thank you very much in advance!

Please find a patch file attached that checks if file tpye is C_TYPE and in that case do the expected format, all other file types will not be affected, hope that will cause the least trouble :)