This project has moved and is read-only. For the latest updates, please go here.

Suggestion on coding

Dec 17, 2014 at 8:02 PM
Hi,

Very apperciated your work and I do enjoy working with it.

Just noticed some coding practice issue, which make bug investigation somehow more difficult: There're quite a lot fields exposed as internal and are directly accessed instead of using the property.

I presume it's for performance consideration, but it's totally unnecessary.
Although I understand, if you use any profiling tool; in VS debug mode, run a timed test; or run a test as debug builds, accessing fields instead of property may give you more than 50% of performance improvement. But in actual release build, they're almost identical in performance.

The compiler optimized it for you.

With property, it's easier to trace source of data, and easier to set breakpoints etc.


Thanks.
-Steven
Dec 22, 2014 at 7:53 AM
Hi,

I have talked to Jan about this comment and we both agree that a class should expose its members via properties. Currently our main focus is to improve the 4.0 version, but we might look into this refactoring in the future.
Dec 22, 2014 at 10:06 PM
Yes, this would be very useful! :D

PD: and that the project will have documentation... I would donate for this! : P

Regards, Nicholls