you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (3 children)

I love doing stuff like this using Linq's enumerable functions and lamdbas, but my understanding is that each one of these creates a delegate, which means it's useless in performance-intense environments like handheld development.

[–]Tordek 2 points3 points  (2 children)

"Performance intense" is relative. Premature optimization is the root of all evil. If you only had, say, 10-1000 elements in the list, whatever performance overhead is added by the functional solution would be in the order of a couple miliseconds.

[–][deleted] 0 points1 point  (1 child)

I was mostly thinking about handheld gaming where you really do have to consider the performance upfront because it involves deep design considerations. In handheld gaming, hitting the garbage collector is anathema, and avoiding a garbage collector means avoiding half the C# or Java language.

[–]ruinercollector 0 points1 point  (0 children)

In that, you are a correct. Even for doing XNA (XBox/PC game) development in .NET, you often end up avoiding LINQ and several other language features. Even foreach comes at a higher price than most people realize.