From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16891 invoked by alias); 24 Jul 2005 04:59:56 -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 16880 invoked by uid 48); 24 Jul 2005 04:59:53 -0000 Date: Sun, 24 Jul 2005 06:28:00 -0000 Message-ID: <20050724045953.16879.qmail@sourceware.org> From: "bangerth at dealii dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050723202503.22635.pinskia@gcc.gnu.org> References: <20050723202503.22635.pinskia@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/22635] OVERLOAD should not be a linked list of trees X-Bugzilla-Reason: CC X-SW-Source: 2005-07/txt/msg03048.txt.bz2 List-Id: ------- Additional Comments From bangerth at dealii dot org 2005-07-24 04:59 ------- I would imagine that in real world, there are either a rather small number of overloads of a name (less than five) or very many (more than 20 or 30). Most code I've seen don't use many overloads (falling into the first class) but there are a few cases in libstdc++, especially in the streams and strings libraries, that use very many overloads. I don't know if knowledge of such overload set size statistics help any in finding an appropriate data structure, though... W. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22635