http://temporalcohesion.co.uk/2007/07/23/limitations-in-delphi/ ...trying not to write legacy code, man. Mon, 07 Jun 2010 13:48:14 +0000 hourly 1 http://temporalcohesion.co.uk/2007/07/23/limitations-in-delphi/comment-page-1/#comment-333 Andrew Tue, 05 May 2009 14:34:24 +0000 http://temporalcohesion.co.uk/2007/07/23/limitations-in-delphi/#comment-333 The idea was to make people aware of the performance gains when using the case statement with ordinal types instead of strings, for strings one could simply use: if SomeString = 'one' then DoSomethingForOne else if SomeString = 'two' then DoSomethingForTwo ... It's not that painful but it would be nice to be able to compare strings and just receive a warning about the performance issue, however we could see this implemented in the OpenSource version of Delphi, Lazarus IDE and the FreePascal compiler which seems to have a lot of interesting features including some level of precompiler macros, operator overloading, CrossPlatform support and many more i'm not sure how generics work in FPC right now but they should be supported soon. On the IDE side Delphi still feels better but maybe things will change in the not so distant future. The idea was to make people aware of the performance gains when using the case statement with ordinal types instead of strings, for strings one could simply use:
if SomeString = ‘one’ then
DoSomethingForOne
else if SomeString = ‘two’ then
DoSomethingForTwo
…
It’s not that painful but it would be nice to be able to compare strings and just receive a warning about the performance issue, however we could see this implemented in the OpenSource version of Delphi, Lazarus IDE and the FreePascal compiler which seems to have a lot of interesting features including some level of precompiler macros, operator overloading, CrossPlatform support and many more i’m not sure how generics work in FPC right now but they should be supported soon. On the IDE side Delphi still feels better but maybe things will change in the not so distant future.

]]>