Date: Tue, 07 Feb 2012 07:29:25 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: dougb@FreeBSD.org Cc: freebsd-rc@FreeBSD.org Subject: Re: Proposal ipv6_addrs_common Message-ID: <20120207.072925.1861639312875773760.hrs@allbsd.org> In-Reply-To: <4F304F54.4020802@FreeBSD.org> References: <4F2F442F.3030509@erdgeist.org> <20120207.064701.1809281571072237708.hrs@allbsd.org> <4F304F54.4020802@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Tue_Feb__7_07_29_25_2012_068)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Doug Barton <dougb@FreeBSD.org> wrote in <4F304F54.4020802@FreeBSD.org>: do> On 02/06/2012 13:47, Hiroki Sato wrote: do> > It actually depends on the newline do> do> That's way too fragile, as users are likely to put them all in one line do> since shell syntax doesn't differentiate (assuming non-wacky values of IFS). I don't think so. In this syntax a newline character is a separator distinguished from normal white spaces by read statement. do> > echo "$foo" | while read L; do echo $L; done do> do> Yeah, don't do that. Aside from the useless fork that you'll cause, you do> can just as easily write: do> do> for L in $foo; do do> do> (Note that $foo is *not* quoted there ...) No, my intention is grouping multiple words by a newline. By using "for", lines cannot be separated from each other in the following case: foo=" foo foo2 bar bar2 baz " -- Hiroki ----Security_Multipart(Tue_Feb__7_07_29_25_2012_068)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAk8wVEUACgkQTyzT2CeTzy279QCgjtlDs5xDJIYsx5SXFBbw6e7c G9kAnjG80yxjGmc5u8TxBsABD9Uoe/hn =wg/A -----END PGP SIGNATURE----- ----Security_Multipart(Tue_Feb__7_07_29_25_2012_068)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120207.072925.1861639312875773760.hrs>