Messages in this thread |  | | | From | "H. Peter Anvin" <> | | Subject | Re: RFC: /proc key naming consistency | | Date | 13 Feb 2002 12:07:05 -0800 |
| |
Followup to: <20020213030047.8B1FB2257B@www.webservicesolutions.com> By author: Mark Swanson <swansma@yahoo.com> In newsgroup: linux.dev.kernel > > Notice the space between "cpu" and "MHz", or "cpu" and "family" yet there is > no space between "fdiv" and "bug" (_). > > The reason I think NOT using a space is a good idea because it makes life > easier for developers parsing /proc entries. Specifically, Java developers > could use /proc/cpuinfo as a property file, but the space in the 'key' breaks > java.util.Properties.load(). >
When I and Dan Quinlan submitted the cleanup for this we used _ everywhere. Unfortunately some other people not just added keys with spaces, but gracefully "corrected" our "mistakes"...
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |