Everybody! This is important. In a few days, these forums will be moving over to using the totally sweet Discourse platform. To ensure this migration happens smoothly with no loss of content, these forums are currently in a read-only mode. I do apologize for the inconvenience.

There is never a good time to turn the forums off for an extended period of time, but I promise the new forums will be a billion times better. I'm pretty sure of it.

See you all on the other side in a few days, and if you have any (non-technical) questions, please e-mail me at kirupa@kirupa.com. For technical questions, try to find a tutorial that corresponds to what you are looking for and post in the comments section of that page.


Results 1 to 3 of 3

Thread: Memory Managment and Exception Handling

  1. #1

    Memory Managment and Exception Handling

    I wonder about Memory Managment and Exception Handling in C#.

    I know that C# has its own "garbage collection" to prevent memory leaks. How does this work and how does someone code accordingly for this? I see that there is still the "new" statement in C# that C++ has for allocating memory for a new object or pointer. Does the "garbage collection" mean that you do not have to have a corresponding "delete" for every "new" statement?

    Do you still have to account for exception handling in C#? Do you still need the "try...catch... throw" blocks? Are them implimented the same way as in C++?

  2. #2
    You don't need exception handling, but I would definitely not leave it out. It's important imo to have exception handling.

    As for garbage collection, and someone correct me if I'm wrong just cause my c# memory is rusty. But garbage collection is only run through at random(?) You should destroy your objects once you've finished with them to free up memory because the gc isn't guranteed to free up memory regularly. I'll add more later if someone hasn't already.

  3. #3
    For the most part, you should never have to manually force the garbage collector to run. Part of the advantage of the .NET framework is that garbage collection is handled for you. If you really want the extra bits of space and can't wait until the automatic collector kicks in, you can start collecting by typing GC.Collect()

    Great, now even Kirupa is { facebooking | twittering }

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Home About kirupa.com Meet the Moderators Advertise

 Link to Us


Copyright 1999 - 2012