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.
- 
        6Honestly, 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.Doc Brown– Doc Brown2020-11-12 23:11:01 +00:00Commented Nov 12, 2020 at 23:11
 - 
        4to 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.Doc Brown– Doc Brown2020-11-12 23:16:04 +00:00Commented Nov 12, 2020 at 23:16
 - 
        4Understanding 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).Ben Cottrell– Ben Cottrell2020-11-13 00:23:07 +00:00Commented 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.Erik Eidt– Erik Eidt2020-11-13 04:01:03 +00:00Commented Nov 13, 2020 at 4:01
 - 
        1There are no cases. You have to learn about memory management, and fix the problems.Stack Exchange Broke The Law– Stack Exchange Broke The Law2020-11-13 15:25:31 +00:00Commented Nov 13, 2020 at 15:25
 
                    
                        
                    
                 | 
            
                Show 1 more comment
            
        
         
    How to Edit
        - Correct minor typos or mistakes
 - Clarify meaning without changing it
 - Add related resources or links
 - Always respect the author’s intent
 - Don’t use edits to reply to the author
 
        How to Format
    
    - 
                create code fences with backticks ` or tildes ~
                ```
like so
``` - 
                add language identifier to highlight code
                ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
 - for linebreak add 2 spaces at end
 - _italic_ or **bold**
 - indent code by 4 spaces
 - backtick escapes 
`like _so_` - quote by placing > at start of line
 - to make links (use https whenever possible)
                <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
 
            How to Tag
        
        A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
 - use tags that describe things or concepts that are essential, not incidental to your question
 - favor using existing popular tags
 - read the descriptions that appear below the tag
 
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
 - creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
 
lang-c