Using Properties

[Devin Dow]

Should I be storing a property in a temporary variable for performance reasons?

Example:
Assume MyClass has a Property called Center that is CPU intensive to calculate.

Would this:

if (MyClass.Center.x > 0 || MyClass.Center.y > 0) ...

take twice as long as this:

Point temp = MyClass.Center;
if (temp.x > 0 || temp.y > 0) ...

or does to compiler take care of this situation?

[Devin Dow]

I tested it myself... Yes it gets called twice and thus takes twice as
long.

"Devin Dow" <de***@rsi-inc.com> wrote in message news:u5****************@TK2MSFTNGP09.phx.gbl...Should I be storing a property in a temporary variable for performance reasons?
Example:
Assume MyClass has a Property called Center that is CPU intensive to calculate.
Would this:

if (MyClass.Center.x > 0 || MyClass.Center.y > 0) ...

take twice as long as this:

Point temp = MyClass.Center;
if (temp.x > 0 || temp.y > 0) ...

or does to compiler take care of this situation?

[Jon Skeet [C# MVP]]

Devin Dow <de***@rsi-inc.com> wrote:

Should I be storing a property in a temporary variable for performance reasons?

Not unless you've already established that this is your performance
bottleneck - which it's unlikely to be.

Yes, the property will be called twice. However, it's likely to be
inlined and the performance hit will be miniscule - but your code ends
up more readable (IMO). Optimisation like this can and should be left
until later.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too