From owner-freebsd-doc@FreeBSD.ORG  Mon Nov 16 23:29:55 2009
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: doc@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 544C91065679
	for <doc@FreeBSD.org>; Mon, 16 Nov 2009 23:29:55 +0000 (UTC)
	(envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46])
	by mx1.freebsd.org (Postfix) with ESMTP id 324348FC19
	for <doc@FreeBSD.org>; Mon, 16 Nov 2009 23:29:55 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 9F35D8C068; Mon, 16 Nov 2009 17:29:54 -0600 (CST)
Date: Mon, 16 Nov 2009 17:29:54 -0600
From: Mark Linimon <linimon@lonesome.com>
To: Rene Ladan <rene@freebsd.org>
Message-ID: <20091116232954.GA6511@lonesome.com>
References: <4B01D5C9.4080207@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B01D5C9.4080207@freebsd.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: doc@FreeBSD.org
Subject: Re: [RFC] [patch] Clang section for Porters Handbook
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2009 23:29:55 -0000

Looks nice.  Here are some ideas.

> 	<para>A future version of &os; will likely have the Clang C/C++
> 	  compiler as its base compiler.  Some modifications to the Ports
> 	  Collection are necessary.  In general, these are <quote>write proper
> 	    ports</quote> and <quote>write proper source code</quote>.

To me, this last sentence is worded a little awkwardly (partly because
of the tense).  How about:

  In general, these involve <quote>generalizing the port</quote> and
  <quote>making the source code portable</quote>.

> 	      so existing occurences have to be removed.  No concensus has yet

  consensus

> 	    <para>The maximum useable optimization level is 3.  Level 4 is

  usable (don't feel bad, I had to look it up)

> 	<para>Some temporary hacks that might be used if all else fails:</para>

I'm almost wondering if the c89 hack might be moved to here, but I'm not sure.

mcl