This is an internal "refactor" and nothing should be affected externally.
This issue should fix the "flow" of WebCrawler where in several places the
method stops suddenly as "return" command is called.
This is done for better code readability (although, this is more of a personal
taste, still most developers prefer one point of exit from a method when it is
not a guarding clause)
This will also enable better understanding of the code in future planned code
changes
Original issue reported on code.google.com by avrah...@gmail.com on 9 Dec 2014 at 9:58
Original issue reported on code.google.com by
avrah...@gmail.com
on 9 Dec 2014 at 9:58