Date: Mon, 4 Jan 1999 05:27:49 -0800 (PST) From: "Eugene M. Kim" <astralblue@usa.net> To: Thomas David Rivers <rivers@dignus.com> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/3246: mtree -c should escape whitespace and special characters Message-ID: <Pine.BSF.4.02A.9901040521050.13812-100000@gw1.pl.cp> In-Reply-To: <199901041256.HAA02103@lakes.dignus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At first I also considered the C-style sequences, but I decided for the URL-style one because the resulting code was simpler (and probably faster). The human readability might be worse, but mtree files are usually read and parsed only by mtree. And the URL-style sequence is already a standard, as defined in RFC2396. On Mon, 4 Jan 1999, Thomas David Rivers wrote: | Eugene... | | I really like the improvements you made to mtree, but I was wondering, | why did you pick "%nn" as the escape? Wouldn't it have been more "C-like" | to use "\nnn","\xnn" and "\c"? I would guess that the backslash is a little | more unlikely as an existing file character (unless we consider Windows)... | | It seems a shame to invent yet-another character escaping mechanism. | | In this case, to note a space, the simple: | | I\ have\ spaces | | would work, and would appear a little more obvious to the reader (those | really are spaces.) | | Similarly, | | I\x20\have\x21special\x22chars | | would work for putting in special characters... | | | Just a thought... | | - Dave Rivers - | Eugene M. Kim <astralblue@usa.net> "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02A.9901040521050.13812-100000>