Timeline for How to migrate my thinking from C++ to C#
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2015 at 19:13 | comment | added | Dunk | With regards to memory management, I found that switching to C# made this more difficult, especially in the beginning. I think you have to be more aware than in C++. In C++ you know exactly when and where every object is allocated, deallocated and referenced. In C#, this is all hidden from you. Many times in C# you don't even realize that a reference to an object has been obtained and memory starts leaking. Have fun tracking down memory leaks in C#, which are usually trivial to figure out in C++. Of course, with experience you learn these nuances of C# so they tend to become less of an issue. | |
| Apr 28, 2015 at 12:54 | comment | added | Telastyn | @rwong - common, but manager classes are still an anti-pattern to be avoided. | |
| Apr 28, 2015 at 11:03 | comment | added | Deduplicator | Regarding shared resources: The managed ones are easy in C# (if race-conditions are irrelevant), the unmanaged ones are far nastier. | |
| Apr 28, 2015 at 7:51 | comment | added | rwong | Regarding resource management, in C# it is quite common to have manager classes (which can be static or dynamic). | |
| Aug 15, 2013 at 2:09 | history | edited | Telastyn | CC BY-SA 3.0 |
added 1477 characters in body
|
| Aug 14, 2013 at 21:03 | history | answered | Telastyn | CC BY-SA 3.0 |