The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

    • RT @samgerrits: Caroline en asielzoekers, een tweeluik. Links: dwepen met een speldje gekregen van een Iraanse asielzoeker, rechts: nou ja… 2 hours ago
    • RT @delphijunkie: Yeah, nah. I'm good thanks Twitter. 2 hours ago
    • RT @d_feldman: Microsoft: We have world class AI research Google: We have world class AI research Meta: We’re one or two steps behind in AI… 2 hours ago
    • RT @SchipholWatch: Op dit moment is kerosine zo’n tien keer goedkoper dan alternatieve synthetische brandstof. De overheid moet dit prijsve… 2 hours ago
    • RT @jasongorman: One aspect of LLMs many folks overlook is the energy cost of training one. GPT-3 used an ~936 MWh and training it took 102… 2 hours ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,178 other subscribers

Archive for August 26th, 2010

Delphi: Optimizing extremely long compile times

Posted by jpluimers on 2010/08/26

Anthony Frazier mentions two very true paths for optimizing your Delphi compile times:

  1. Avoid units with the “read-only” attribute set.
  2. Avoid large circular dependency groups, particularly if you put everything in the interface’s uses clause rather than the implementation uses clause.

To get rid of the second, you should split your interface and your implementation.
Often, one of these two solutions work for that well:

  • Create the interface as a base class, then implement it in a descendant.
  • Create the interface as a Delphi interface, then implement it in a class.

Only if those options do not work, then start using Delphi SpeedUp by Andreas Hausladen.


Via: » Blog Archive » The Power of Open Source.

Posted in Delphi, Development, Software Development | 19 Comments »

%d bloggers like this: