Date: Thu, 27 Sep 2001 11:39:50 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/fs/procfs procfs_status.c Message-ID: <200109271539.f8RFdol02598@khavrinen.lcs.mit.edu> In-Reply-To: <81584.1001578758@axl.seasidesoftware.co.za> References: <20010927145242.B3656@sydney.worldwide.lemis.com> <81584.1001578758@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Thu, 27 Sep 2001 10:19:18 +0200, Sheldon Hearn <sheldonh@starjuice.net> said: > If you're suggesting hex, which requires fewer characters to represent, > I'm with you. Depending on whether or not you want to be compatible with C syntax, octal may be preferable to hex. The reason is that C's octal escapes never represent more than one character; C's hex escapes can code for an unlimited number of characters. This means that any character following a hex escape which might be interpreted as a valid hexadecimal digit must also be escaped. (I.e., "\xffff" represents the same string literal as "\277\277", not "\277ff".) I would suggest that the vis(3) default encoding should be used. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109271539.f8RFdol02598>