Date: Thu, 27 Sep 2001 18:14:54 +0300 From: Peter Pentchev <roam@ringlet.net> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: Greg Lehey <grog@FreeBSD.org>, Mike Barcroft <mike@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/fs/procfs procfs_status.c Message-ID: <20010927181454.C658@ringworld.oblivion.bg> In-Reply-To: <81584.1001578758@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Thu, Sep 27, 2001 at 10:19:18AM %2B0200 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, Sep 27, 2001 at 10:19:18AM +0200, Sheldon Hearn wrote: > > > On Thu, 27 Sep 2001 14:52:42 +0930, Greg Lehey wrote: > > > > Log: > > > A process name may contain whitespace and unprintable characters, > > > so convert those characters to octal notation. > > > > Why octal? > > If you're suggesting hex, which requires fewer characters to represent, > I'm with you. But does it really require fewer characters? Keep in mind that only a couple of the characters in the process's name are represented this way; they have to be properly designated as 'special'. The traditional way to do this is to escape them in some way, e.g. with a \ before the special code. After a \, it is customary to put three octal digits or a 'x' followed by two hex digits - both of those come up to three characters. If you are suggesting a \ or some other character to be immediately followed by two hex digits, then this would stretch the existing traditions for designating special characters, and it would look weird, at least to me.. G'luck, Peter -- because I didn't think of a good beginning of it. 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?20010927181454.C658>