From owner-freebsd-current@FreeBSD.ORG Mon Mar 15 11:57:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E6E416A4CE for ; Mon, 15 Mar 2004 11:57:59 -0800 (PST) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63E7D43D1D for ; Mon, 15 Mar 2004 11:57:58 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i2FJvrUe017702; Tue, 16 Mar 2004 06:57:53 +1100 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i2FJvoGi024168; Tue, 16 Mar 2004 06:57:51 +1100 Date: Tue, 16 Mar 2004 06:57:50 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= In-Reply-To: Message-ID: <20040316063436.G8024@gamplex.bde.org> References: <6.0.1.1.1.20040314234126.03adbc50@imap.sfu.ca> <6.0.1.1.1.20040315164047.03bd0ea8@imap.sfu.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE cc: Thomas Dickey cc: current@freebsd.org cc: Colin Percival Subject: Re: spaces before tabs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 19:57:59 -0000 On Mon, 15 Mar 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote: > Thomas Dickey writes: > > #define longstring "This is a string \ > > =09that does not really have \"leading blanks\", per \ > > =09se, but some scripts may have other opinions" Would you object to changing the formatting bugs in the string literal (embedded tabs)? :-) Misformatting of user-visible message is a larger bug than misformatting of source code. > this is one of the reasons why our style guidelines prohibit multiline > string literals. Actuallly, there is no such prohibition, and multiline string literals are normal style -- they are used in every CSRG copryright message in the src tree. There is only a C language prohibition on hard newlines in string literals (*). The above is not an example of this. (*) Hard newlines in string literals used to be a gcc feature, but gcc-3 dropped it, apparently without providing a flag to give backwards compatible behaviour. Bruce