Object Oriented Development vs Practicality

[TheMonkey]

Surely this won't cause endless recursion?

No it doesn't. It just sticks 2 things on the call stack and 2 out of scope operations to increment a value. Effectively it runs:

void set_Property(int value) { this.property = value; }
int get_Property() { return this.property; }

set_Property(get_Property() + 1);

Stick it in a loop - blam! Crap performance. I'd compile it and dump the IL code out using reflector but I'm on a mac at the moment and playing with Objective C instead.

I don't like properties - they obscure some performance problems.

[Diestl]

Why use C# if you're only interested in performance, use C++ or C. Things like properties are there to allow proper object oriented implementation.

[TheMonkey]

Why use C# if you're only interested in performance, use C++ or C. Things like properties are there to allow proper object oriented implementation.

Very insightful!

[Diestl]

thanks

[TheMonkey]

thanks

My pleasure.

I entirely agree with your point. I'm actually learning Objective C at the moment (OO layer on top of C basically). Less convoluted than C++...

[AtW]

Yeah properties are performance killer - strange that they are not inlined. Performance wise C# is actually very good - I had some stuff ported to Visual C++ and assembly code generated was not much better.

[Jabberwocky]

Horseshi*t - properties are fine if used in the proper context e.g. graphical components - only an half-ar*ed ruskie would be getting and setting in a performance critical loop involving no other opertations - they are only a few mc ops anyway.

[AtW]

Go look at something shiny jabber.

[Jabberwocky]

Are you some sort of magpie AtW ? I suggest you go back to school and get a proper comp sci education.

[TheMonkey]

Are you some sort of magpie AtW ? I suggest you go back to school and get a proper comp sci education.

Like my electrical engineering one

We're not all native comp sci.