From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25524 invoked by alias); 8 Apr 2009 19:32:10 -0000 Received: (qmail 25497 invoked by uid 48); 8 Apr 2009 19:32:00 -0000 Date: Wed, 08 Apr 2009 19:32:00 -0000 Message-ID: <20090408193200.25496.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/25185] deep typedef substitution in error message In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jason at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-04/txt/msg00772.txt.bz2 ------- Comment #27 from jason at gcc dot gnu dot org 2009-04-08 19:31 ------- I've gone ahead and checked in the -fno-pretty-templates patch, which should produce ../../../../boost/sequence/make_range.hpp:60: instantiated from ‘boost::sequence::detail::range_maker, boost::array > >::range > boost::sequence::detail::range_maker, boost::array > >::operator(), const boost::array > >(const boost::sequence::identity_property_map&, char* const&, char* const&, const boost::sequence::detail::size_difference, const boost::array >&) const’ where compiling without that flag gives ../../../../boost/sequence/make_range.hpp:60: instantiated from ‘boost::sequence::detail::range_maker::type boost::sequence::detail::range_maker::operator()(const L&, const B&, const E&, const C&) const [with L = boost::sequence::identity_property_map, B = char*, E = char*, C = boost::sequence::detail::size_difference, const boost::array >, Elements = boost::sequence::identity_property_map, Begin = char*, End = char*, CalcSize = boost::sequence::detail::size_difference, boost::array >, boost::sequence::detail::range_maker::type = boost::sequence::range_::range >]’ so you can choose which one you want. I think typedef handling still isn't perfect after these issues; we only strip typedefs at the top level, and may still print class-scope typedef names in other contexts, especially since the work to do access control on typedefs in templates means that class-scope typedefs get a variant type now, so the typedef name is visible to the diagnostic code in a lot of cases where it wasn't previously. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25185