1
vote
Vote UpVote

Reminder to self: be aware of implicit setup/tear down code in methods

The Wiert Corner – If a part of a method requires implicit setup/tear-down code (for instance when using managed types like arrays, strings, etc), especially in rarely taken execution paths, then consider putting that code in a separate method. I bumped into this recently, and found out it does not just hold for Delphi, it can happen in other languages too. A Delphi example I found back is this one: [WayBack] Delphi Corner Weblog: Speed problems caused by code that never ran. The problem with Delphi is that the language does not have local scope (variables are at the start of the method) which means the penalty ...
Favorite? Off-Topic? jpluimers @ 2020-02-13 06:04

Statistics

Visits: 92
Votes: 1
Favorites: 0
Off-Topic: 0

Visits by Source

User Actions

Users who voted for this posting

Michał Rajewicz
Subscribe:
Contact us to advertise on DelphiFeeds.com

Community Links

Torry Firebird News

Sponsor

 
Please login or register to use this functionality.
(click on this box to dismiss)