інтуітивність імперативного

[sassa_nf]

Тут хтось поскаржився, що порядок обчислень в Х-і не зрозумілий. Ну, ось вам імперативний варіант, не обляпайтесь:

function walk2(preorder, inorder

Comments

[nivanych]

> не обляпайтесь:

Кусаю крупные куски, жЫр во все стороны, вкуснотищщаа!
Ой, обляпался...
;-)

[ex_juan_gan]

Well, weird; first I asked myself if we roll it all back and try to write it immutably, that is, start building the tree starting from leaves... then I figure, it was my solution (big deal, use call stack instead)

[sassa_nf]

What I find weird is that the immutable solution forces you to look at it inductively. You start expressing yourself in terms of subtrees (how do we know we have the whole left subtree for a node; how do we know we have the whole right subtree), because you can no longer think about "setting" pointers, or tweaking them later.

This imperative piece was obtained to see if we can do the same in reverse.

[ex_juan_gan]

Right. Just all my experience with mutable pointers tells me - it's a hell.

[nponeccop]

Да даже удаление элемента из середины двунаправленного списка.