Smarty

[pedrotester]

That doesn't answer my question, I still have to do twice the same thing. Is it normal? yes or no, no riddle plz

[AnrDaemon]

No, it's not the same thing.
If my answer "doesn't answer your question", then google the difference yourself.

[bsmither]

A multi-level parent->child hierarchy of similar structure is the very definition of recursion. (See: fractal)

Technically, you don't need to recurse. You can do the same with a massive amount of repetitive code. But doing that would require you to have an intimate knowledge of the nature of your source data. For example, you know for a fact that you only have, and only will ever have, at most, three generations of relationships with three siblings in each generation.

And if that is your intended structure - three generations - then massive amounts of repeating code would suffice.

The problems start when you need to change some aspect of each sibling. Change massive numbers of instances - or just one that gets recursed (or is a function call).

So, use recursion to construct your hierarchical structure, and use recursion to deconstruct that structure into the required displayable orientation/organization.

This is a general programming (problem-solving) task -- breaking a large pattern into manageable, repeatable, smaller and identical patterns.

[pedrotester]

thank you for explanation!