The Bad Delphi Code Competition - winners announced!

-
The Bad Delphi Code Competition - winners announced!

There were some very creative and really terrible entries. Read the post for seven of them, plus the winners! Not to be clickbait, but the kind of code some people wrote (and the ingenuity it showed) may surprise you...

https://parnassus.co/delphi-bad-code-competition-results-winners/
https://parnassus.co/delphi-bad-code-competition-results-winners

Comments

  1. Thomas Mueller (dummzeuch)March 24, 2016 at 11:14 AM

    Congrats to the winners! Excellent examples of bad code.
    Can we also have a look at the other entries to the competition? I'm surprised that nobody took the scope problem to the extreme using units, classes, local variables, variables in nested procedures and various levels of with statements. But on the other hand, maybe there were such entries but you decided the ones you listed were worse than that debugging nightmare.

    ReplyDelete
  2. David MillingtonMarch 25, 2016 at 4:27 AM

    Thomas Mueller I published most of the entries - there were some small snippet entries, but all the big projects were published. In Wouter van Nifterick's BreakStuff, he did comment that you could put the Break method in a different unit to make it more confusing. No-one submitted anything with the extreme confusion of units, classes, variables, nested withs, etc that you suggest though.

    ReplyDelete
  3. Thaddy de KoningMarch 25, 2016 at 7:47 AM

    Wouter deserves special mention! I found some more oddities in the same category playing with his  ' pointer"
    There are more, but Like
    const
       true:boolean = system.false;
       false: boolean = system.true;.

    function Odd(a:integer):boolean;
    begin
       Result := not system.odd(a);
    end;

    Put all that in a unit as Wouter suggested and add it to your ciollegues uses clause at April Fool's day ;) .

    ReplyDelete

Post a Comment