There are currently some unit tests for the GExperts code formatter that fail. It all depends on how spaces after comments {comment} or (*comment*) are handled.   A How should the code formatter handle the following code: procedure bla; begin {some comment} SomeStatement; end; A1 Keep the space after the comment: procedure bla; begin   {some comment} SomeStatement; end; A2 Remove the space after the comment: procedure bla; begin   {some comment}SomeStatement; end;   B what about this code: procedure bla; begin {some comment}SomeStatement; end; B1 should the formatter leave it as is? B2 should it insert a space, so it gets changed into: procedure bla; begin   {some comment} SomeStatement; end;   C what about this code with multiple spaces after the comment: procedure bla; begin {some comment} SomeStatement; end; C1 should the formatter remove the spaces: procedure bla; begin {some comment}SomeStatement; end; C2 or should it reduce them to one space: procedure bla; begin {some comment} SomeStatement; end; C3 or should it leave them as them as they are: procedure bla; begin {some comment} SomeStatement; end;   The current code will always remove the spaces, so its A2, B1 and C1.   I'm tending towards keeping the number of spaces as they are, that would be A1, B1 and C3.   I'm definitely not going to make this configurable. I wouldn't even know how to describe this configuration option.