Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 6
    Honestly, I have no idea why you think splitting up your code in the described way would reduce and of the current bugs. In fact, I would expect such a redesign require a lot of additional interprocess communication, which has potential for introducing new bugs. Commented Nov 12, 2020 at 23:11
  • 4
    to become familiar with memory management will take a long time, which I just don't have right now - that is most probably a fallacy, since if you don't take the time for learning proper memory management, you will have to invest even more time into testing and debugging. Commented Nov 12, 2020 at 23:16
  • 4
    Understanding memory management is non-optional for being able to wield the C language effectively since it's prerequisite knowledge for using a lot of essential C language features properly. If you'd prefer to avoid that, then consider using a different language altogether which takes care of memory for you (e.g. Python, C#, Java); indeed, unless you have a very specific reason for using C then it's generally not recommended as a beginner language (for this exact reason, as well as the general low-level nature of the C language making it far less beginner-friendly than Java/Python/etc). Commented Nov 13, 2020 at 0:23
  • 1
    "Understanding memory mangement" There's not much to know: (1) don't use after free'ing (that includes double free'ing), and, (2) if you never free, you'll have a memory leak. So, free just at a good time, not too soon, and not never. Commented Nov 13, 2020 at 4:01
  • 1
    There are no cases. You have to learn about memory management, and fix the problems. Commented Nov 13, 2020 at 15:25