Re: [Neo] Side effect

Hi Mattias Cool, you guys do get stuff fixed fast. All the best Neil On 28 Jul 2009, at 12:10, Mattias Persson wrote: > I just committed a fix for it (rev. 3017) ... it should do the trick > > 2009/7/28 Mattias Persson : >> You're absolutely right... I see the problem in the iterator >> impleme

Re: [Neo] Side effect

I just committed a fix for it (rev. 3017) ... it should do the trick 2009/7/28 Mattias Persson : > You're absolutely right... I see the problem in the iterator > implementation of that method. I or Johan will fix that soon. > > 2009/7/27 Neil Ellis : >> Hi guys >> >> I noticed a side-effect in the

Re: [Neo] Side effect

You're absolutely right... I see the problem in the iterator implementation of that method. I or Johan will fix that soon. 2009/7/27 Neil Ellis : > Hi guys > > I noticed a side-effect in the iterator for all nodes. > > If you do not do a hasNext() before a next() you get a no such element > except

[Neo] Side effect

Hi guys I noticed a side-effect in the iterator for all nodes. If you do not do a hasNext() before a next() you get a no such element exception. So even if I have a million nodes .next() on the first node throws an exception, unless I do a hasNext() check first. I believe a hasXXX() method