Date: Fri, 9 May 2008 16:35:12 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= <romain@blogreen.org> To: hackers@freebsd.org, freebsd-hackers@freebsd.org Cc: Romuald Conty <romuald.conty@free.fr> Subject: Re: indent(1) support for gcc(1) 0b prefix Message-ID: <20080509143512.GA69792@marvin.blogreen.org> In-Reply-To: <481A959C.5000704@freebsd.org> References: <20080426213557.GA88577@marvin.blogreen.org> <200804270201.53271.max@love2party.net> <8763txlaj6.fsf@kobe.laptop> <481A959C.5000704@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 01, 2008 at 09:16:28PM -0700, Tim Kientzle wrote: > In all of these cases, though, adding a space between the '0' and > the 'b' changes the meaning, so is wrong. Indent can > change/insert whitespace, but should never do so in a way that > changes the meaning of the program. In all of these cases, > having indent recognize "0b..." as a single token is the > correct behavior. >=20 > So I don't see any point in having this recognition be > tunable. indent already has too many switches. I oppened PR bin/123553 concerning this: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D123553 Regards --=20 Romain Tarti=E8re <romain@blogreen.org> http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgkYSAACgkQ2OmjP/9W/0M6yACfZAg1lu6NgZcjrVewK1DflZqK ww4An3k2jAZuf5g6iE0JR8L4ZJ+kRnMU =66rh -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080509143512.GA69792>