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.
Required fields*
- 
        2Some problems are simply more naturally expressed using recursion. Tree traversal, for example.Frank Hileman– Frank Hileman2017-04-24 21:06:27 +00:00Commented Apr 24, 2017 at 21:06
 - 
        Updated my answer to address that point,Stephen C– Stephen C2017-04-25 01:16:25 +00:00Commented Apr 25, 2017 at 1:16
 - 
        1With regards to "naturalness": tree traversal without recursion, for example, tends to produce larger, less general purpose code. Consider for example using polymorphic calls to traverse the tree, with different behavior for leaf and composite nodes. This is not possible without recursion.Frank Hileman– Frank Hileman2017-04-25 13:41:38 +00:00Commented Apr 25, 2017 at 13:41
 - 
        1) Did you take up my challenge to define "natural" yet? 2) Since it is possible to simulate recursion using a stack data-structure, it is possible to implement tree traversal that way too. It may not be the most efficient way ... and it won't give you the most readable code ... but it is definitely possible, and practical to do it.Stephen C– Stephen C2017-04-25 14:12:35 +00:00Commented Apr 25, 2017 at 14:12
 - 
        By the way, the first programming language that I learned (FORTRAN 4) did not support recursion at all.Stephen C– Stephen C2017-04-25 14:15:09 +00:00Commented Apr 25, 2017 at 14:15
 
                    
                        
                    
                 | 
            
                Show 4 more comments
            
        
         
    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