From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21704 invoked by alias); 3 Aug 2004 15:16:12 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 21688 invoked by alias); 3 Aug 2004 15:16:11 -0000 Date: Tue, 03 Aug 2004 15:16:00 -0000 Message-ID: <20040803151611.21687.qmail@sourceware.org> From: "gdr at integrable-solutions dot net" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040610143911.15910.king.benjamin@mh-hannover.de> References: <20040610143911.15910.king.benjamin@mh-hannover.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/15910] can't compile self defined void distance(std::vector, std::vector) X-Bugzilla-Reason: CC X-SW-Source: 2004-08/txt/msg00212.txt.bz2 List-Id: ------- Additional Comments From gdr at integrable-solutions dot net 2004-08-03 15:16 ------- Subject: Re: can't compile self defined void distance(std::vector, std::vector) "bangerth at dealii dot org" writes: [...] | [1] What does make me nervous, though, is the following: if the standard | _allows_ us to check constraints on template parameters, and we do | so, then the program in this PR will become valid. However, it will not | necessarily become portable: other compiler libraries may not follow | this "allows to" clause, and this program will not be compilable there. Indeed. That is why I would prefer it b a requirement, not mere allowance. Mere allowance is a royal route to non portability :-( | This is why I would much rather prefer if the standard actually prescribed | the correct signature of std::distance, as this is the only way to make | sure that programs remain compatible. We're in violent agreement. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15910