Optimising as you programme

[Leledumbo]

* How many times would you need to call a property before its better to cache it locally ?  That would, IMHO, depend on the type too, the cost of declaring an integer and copying data to it would be less than, say a string (that is generally a managed ANSIString for most of us).

Me: Everytime. First, always locally cache property calls will save you from guesswork whether that property is mapped to a method or mere field. Second, usually a property call is a long chain (e.g.: AListBox.Items.Count), save some typing as you may not know eventually how many times it will be called.

[Arioch]

Second, usually a property call is a long chain (e.g.: AListBox.Items.Count), save some typing as you may not know eventually how many times it will be called.

Third, if you eventually decide you needed some other property/control - you only have change one place, not dozen :-)

and that is where i miss one-addignment variables, like in functional languages or val vs var in Scala. I think newer Delphi tackled it with letitng consts be declared in every begin-end like in C, or maybe not. Can i have procedure .... begin ... begin const SL = Self.Memo1.Lines; SL.Clear; ... in Delphi 10.x ? Don't know.