Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /homepages/2/d43022721/htdocs/clickandbuilds/twmsblog/wp-content/themes/suffusion/functions/media.php on line 666

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /homepages/2/d43022721/htdocs/clickandbuilds/twmsblog/wp-content/themes/suffusion/functions/media.php on line 671

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /homepages/2/d43022721/htdocs/clickandbuilds/twmsblog/wp-content/themes/suffusion/functions/media.php on line 684

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /homepages/2/d43022721/htdocs/clickandbuilds/twmsblog/wp-content/themes/suffusion/functions/media.php on line 689

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /homepages/2/d43022721/htdocs/clickandbuilds/twmsblog/wp-content/themes/suffusion/functions/media.php on line 694
GExperts formatter bug fixed, waiting for code sample which made the change necessary – twm's blog
Nov 112012
 

Uli Gerhard found a bug which was introduced in the last version of GExperts. It resulted in code after class declarations in the implementation section to be formatted incorrectly:

unit SomeUnit;

interface

implementation

type
  TSomeClass = class
    constructor Create;
  end;

constructor TSomeClass.Create;
begin
end;

end.

During the formatting, the space between constructor and TSomeClass.Create was removed which resulted in uncompilable code.

I think I found and fixed the problem, but I am waiting for Jens Borrisholt to provide a code example that actually needed this code to be formatted correctly, so there will be no new release yet.

 Posted by on 2012-11-11 at 15:05