From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21808 invoked by alias); 2 Aug 2010 23:45:34 -0000 Received: (qmail 21796 invoked by uid 22791); 2 Aug 2010 23:45:33 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 02 Aug 2010 23:45:28 +0000 Received: (qmail 25489 invoked from network); 2 Aug 2010 23:45:26 -0000 Received: from unknown (HELO ?192.168.5.198?) (mitchell@127.0.0.2) by mail.codesourcery.com with ESMTPA; 2 Aug 2010 23:45:26 -0000 Message-ID: <4C575891.1000106@codesourcery.com> Date: Mon, 02 Aug 2010 23:45:00 -0000 From: Mark Mitchell User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Richard Kenner CC: stevenb.gcc@gmail.com, Joe.Buck@synopsys.com, ams@gnu.org, bkoz@redhat.com, dewar@adacore.com, dnovillo@google.com, gcc@gcc.gnu.org, iant@google.com, richard.guenther@gmail.com Subject: Re: GFDL/GPL issues References: <4BFC6EF0.4090908@codesourcery.com> <20100726175013.20b12428@shotwell> <4C4E35B8.6010301@codesourcery.com> <4C4E37FC.1060208@adacore.com> <4C4F010C.5060401@codesourcery.com> <20100727180738.GU17485@synopsys.com> <4C4F20E8.5050206@codesourcery.com> <4C509E54.6090401@codesourcery.com> <11007291247.AA02219@vlsi1.ultra.nyu.edu> <4C5195FA.2060208@codesourcery.com> <4C52B176.7040807@adacore.com> <4C52E1C0.6090400@codesourcery.com> <4C53696B.7030801@adacore.com> <4C536B50.4010402@codesourcery.com> <11008022335.AA09107@vlsi1.ultra.nyu.edu> In-Reply-To: <11008022335.AA09107@vlsi1.ultra.nyu.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-08/txt/msg00018.txt.bz2 Richard Kenner wrote: >> That is true, but very often the documentation is needed in two >> places: in the code and in the manual. Especially for things like >> machine constraints, flags and options. > > Yes, but the audiences are different between users who read the manual and > developers who read the code. Richard, your argument is a distraction from the important issue at hand. Unless you posit that there is no useful way in which to generate documentation from code (and comments therein), which seems an extreme statement, then it is desirable that we have the ability to do that. Right now we don't. That's bad. I certainly don't disagree that it might be desirable for documentation for constraints might be different for end users and for GCC developers. But, there is nothing that says that both kinds of documentation might not be located physically in the code, so that when you add/delete/modify a constraint you can also easily update the documentation. And, furthermore, just because it might be desirable for the documentation to be different for end-users and compiler developers doesn't mean that it's practical for them to be different. I don't see a mob of people beating down the doors to write GCC documentation. So, I'm not inclined to let perfect be the enemy of good. If we only get one "flavor" of documentation, that's a lot better than none at all! In any case, the key issue here isn't how we should write documentation. It's whether we can use a technological measure to generate documentation if we find cases where that is desirable. It makes no sense for the FSF to artificially erect legal barriers to using a given technical approach to creating documentation. If this is really about documentation quality, the FSF could simply have a policy saying that GNU maintainers should not do this -- there is no reason to have a legal prohibition preventing people from doing it! -- Mark Mitchell CodeSourcery mark@codesourcery.com (650) 331-3385 x713