(sending again as I made a type in the email.)
Søren,
I was surprised to find necessity to invoke has_next as otherwise iterator
goes
wild.
For now I fixed it by stupid it.has_next() invocations. More principal
approach
could be to blend has_next and next into one method (e.g. making next
return 0
when space is exhausted.) If you think it's a reasonable idea, I'd
willingly
implement it, but I'd prefer to do that in another CL to ease rolling back
if
need would be.
http://codereview.chromium.org/552066
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
