{"id":27887,"date":"2022-12-27T08:13:44","date_gmt":"2022-12-27T02:43:44","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-recursion-java-return-with-some-tree-strcuture\/"},"modified":"2022-12-27T08:13:44","modified_gmt":"2022-12-27T02:43:44","slug":"solved-recursion-java-return-with-some-tree-strcuture","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-recursion-java-return-with-some-tree-strcuture\/","title":{"rendered":"[Solved] Recursion java return with some tree strcuture"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

To answer your question, yes it would make a huge difference if you removed the return<\/code> statement from your return children.get(i).search(x);<\/code> line of code.<\/p>\n

The method signature:<\/p>\n

public Node search(int x)\n<\/code><\/pre>\n
specifically states that it will return a node value, therefore the end result of this method must return a Node, or a null value.<\/p>\n
“How does java handle these statements differently?”<\/strong><\/p>\n
The method call: children.get(i).search(x);<\/code> merely runs the method and moves on. This only works if the method has a void return type. Since your method returns a value (in this case a Node) you have to do something with the value.<\/p>\n
Calling a method that returns a value is like using a variable in a sense.<\/p>\n
You can’t just have a line of code that says:   variableX;<\/code><\/p>\n
You need to do something with it. In your case, since your method returns a Node type, you’ve got to do something with the returned value when you call the method.<\/p>\n
In order for this algorithm to work, you’re taking the value obtained from the called method, and returning it back to the calling method.<\/p>\n
Using a visual example:<\/p>\n
Search1 > Search2 > Search3<\/p>\n