[Bug libstdc++/15910] can't compile self defined void distance(std::vector<T>, std::vector<T>)

[pinskia at physics dot uc dot edu]

------- Additional Comments From pinskia at physics dot uc dot edu  2005-08-12 02:14 -------
Subject: Re:  can't compile self defined void distance(std::vector<T>, std::vector<T>)

> 
> 
> ------- Additional Comments From adah at netstd dot com  2005-08-12 02:10 -------
> (In reply to comment #79)
> > Subject: Re:  can't compile self defined void distance(std::vector<T>, 
> std::vector<T>)
> > "adah at netstd dot com" <gcc-bugzilla@gcc.gnu.org> writes:
> >  
> > | > Furthermore, and more importantly, GCC bugzilla is the not the place
> > | > to record UNEXPECTED or PROBLEM with the C++ standard.
> > | 
> > | Is it a guideline of GCC Bugzilla that a PRoblem owing to the C++ Standard 
> is 
> > | never considered a PRoblem at all? 
> >                       
> > Ahem.  Can you read?
> 
> Show an official page.
http://gcc.gnu.org/bugs.html

"In particular, bugs caused by invalid code have a simple work-around: fix the code."

"With each release, we try to make G++ conform closer to the ISO C++ standard (available at http://www.ncits.org/cplusplus.htm). We have also implemented some of the core and library defect reports (available at http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html & http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html respectively)."

http://gcc.gnu.org/gcc-3.4/changes.html

"GCC 3.4 has many improvements in the C++ frontend. Before reporting a bug, please make sure it's really GCC, and not your code, that is broken."

There are more.

-- Pinski


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15910