[Insight-developers] itkImageConstIteratorWithIndex.h

[Joshua Cates]

I agree.  This sounds like a bug to me.

Josh.


On Wed, 23 Apr 2003, Miller, James V (Research) wrote:

> I think your examples should both print 1.
> 
> So if possible (without breaking existing code), I would change the code. A
> call to IsAtBegin() should return true if it is called immediately after a
> GoToBegin(). Same for "end" versions.
> 
> 
> 
> > -----Original Message-----
> > From: Mark Foskey [mailto:mark_foskey@unc.edu]
> > Sent: Wednesday, April 23, 2003 12:12 PM
> > To: insight-developers@public.kitware.com
> > Subject: [Insight-developers] itkImageConstIteratorWithIndex.h
> > 
> > 
> > In itkImageConstIteratorWithIndex.h, both IsAtBegin() and IsAtEnd() 
> > return !m_Remaining.  It appears that
> > 
> >    it.GoToBegin();
> >    std::cout << it.IsAtBegin() << std::endl;
> > 
> >    it.GoToEnd();
> >    std::cout << it.IsAtEnd() << std::endl;
> > 
> > will both print 0.  Do we at least want to document this behavior?  I 
> > can imagine scenarios where you might want to test whether an 
> > iterator 
> > has been incremented since GoToBegin() was called, although I think 
> > they would be rare.
> > 
> > -- 
> > Mark Foskey    (919) 843-5436  Computer-Aided Diagnosis and 
> > Display Lab
> > mark_foskey@unc.edu            Department of Radiology, CB 7515, UNC
> > http://www.cs.unc.edu/~foskey  Chapel Hill, NC  27599-7515
> > 
> > _______________________________________________
> > Insight-developers mailing list
> > Insight-developers@public.kitware.com
> > http://public.kitware.com/mailman/listinfo/insight-developers
> > 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers
>