From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12730 invoked by alias); 6 Aug 2003 16:35:22 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 12723 invoked from network); 6 Aug 2003 16:35:22 -0000 Received: from unknown (HELO piper.synopsys.com) (198.182.56.5) by sources.redhat.com with SMTP; 6 Aug 2003 16:35:22 -0000 Received: (from jbuck@localhost) by piper.synopsys.com (8.11.6/8.11.6) id h76GYmO05820; Wed, 6 Aug 2003 09:34:48 -0700 Date: Wed, 06 Aug 2003 16:51:00 -0000 From: Joe Buck To: Robert Dewar Cc: mrs@apple.com, gcc@gcc.gnu.org, gdr@integrable-solutions.net Subject: Re: On inlining in C++ Message-ID: <20030806093448.A5809@synopsys.com> References: <20030806030112.7D289F2DC1@nile.gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030806030112.7D289F2DC1@nile.gnat.com>; from dewar@gnat.com on Tue, Aug 05, 2003 at 11:01:12PM -0400 X-SW-Source: 2003-08/txt/msg00383.txt.bz2 On Tue, Aug 05, 2003 at 11:01:12PM -0400, Robert Dewar wrote: > > excessive lookahead (call comes before the > > definition) > > This actually seems like a pretty serious limitation to me ... Given that we can't inline mutually recursive functions, it is always possible to fix the order so that things work, though it can be a pain in the ass.