Re: [Boost-bugs] [Boost C++ Libraries] #2009: suggested resiliency/ease-of-use

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2009: suggested resiliency/ease-of-use
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-06-14 09:17:11

#2009: suggested resiliency/ease-of-use
-------------------------------+--------------------------------------------
  Reporter:  dave              |       Owner:  nesotto
      Type:  Feature Requests  |      Status:  new    
 Milestone:  Boost 1.36.0      |   Component:  range  
   Version:  Boost 1.35.0      |    Severity:  Problem
Resolution:                    |    Keywords:         
-------------------------------+--------------------------------------------
Comment (by anonymous):

 I could "fix" the code for range2 by adding one typedef:

   struct range2
   {
       range2() {}

       typedef char* iterator;
       typedef iterator const_iterator; // this one added
       char* begin() const { return 0; }
   };


 Is that good enough, or do you still think it is a big problem that two
 versions of range_begin() needs to be defined?

 -Thorsten

-- 
Ticket URL: <http://svn.boost.org/trac/boost/ticket/2009#comment:1>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.