From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24414 invoked by alias); 20 Jan 2004 12:36:27 -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 24401 invoked from network); 20 Jan 2004 12:36:25 -0000 Received: from unknown (HELO vlsi1.ultra.nyu.edu) (128.122.140.213) by sources.redhat.com with SMTP; 20 Jan 2004 12:36:25 -0000 Received: by vlsi1.ultra.nyu.edu (4.1/1.34) id AA06794; Tue, 20 Jan 04 07:38:39 EST Date: Tue, 20 Jan 2004 12:36:00 -0000 From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Message-Id: <10401201238.AA06794@vlsi1.ultra.nyu.edu> To: s.bosscher@student.tudelft.nl Subject: Re: [RFC] Contributing tree-ssa to mainline Cc: gcc@gcc.gnu.org X-SW-Source: 2004-01/txt/msg01478.txt.bz2 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.