From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12261 invoked by alias); 20 Jan 2004 15:06:16 -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 12248 invoked from network); 20 Jan 2004 15:06:16 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 20 Jan 2004 15:06:16 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AixSJ-00032Q-El for ; Tue, 20 Jan 2004 10:06:15 -0500 Date: Tue, 20 Jan 2004 15:06:00 -0000 From: Daniel Jacobowitz To: gcc@gcc.gnu.org Subject: Re: [RFC] Contributing tree-ssa to mainline Message-ID: <20040120150615.GA1348@nevyn.them.org> Mail-Followup-To: gcc@gcc.gnu.org References: <10401201238.AA06794@vlsi1.ultra.nyu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10401201238.AA06794@vlsi1.ultra.nyu.edu> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-01/txt/msg01500.txt.bz2 On Tue, Jan 20, 2004 at 07:38:39AM -0500, Richard Kenner wrote: > It's not a replacement for real documentation (that we're also working > on) but it makes the code much easier to understand. And you don't > have to grep so much, if you see a functions you don't know yet, just > follow a link and see what it does. > > I would *much* prefer to see all documentation in the sources. The code needs > to be self-contained and not to web pages someplace. If you print out > a set of files to read on an airplane, for example, you want to have all > the necessary documentation in those files. Did you take a look at it? You've been given at least three links to it already. It is extracted from the sources via doxygen. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer