From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Mon, 23 Apr 2007 18:20:58 -0500 Subject: [U-Boot-Users] RFC: hidden environment variables In-Reply-To: <20070423215158.808153535D2@atlas.denx.de> References: <20070423215158.808153535D2@atlas.denx.de> Message-ID: <462D3F5A.1040307@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: > In message <462D1703.9000907@freescale.com> you wrote: >>> Why would you want to hide them? >> To provide internal storage for functionality (in this case, a command >> to manage non-probeable jumpers and such) without exposing the storage >> format. > > What would be bad about this? If I want to know the format, I just > look it up in the source code. You cannot hide that. The level of hiding that you're talking about is more extreme than the level we're talking about. We're just talking about not having the variable show up when you do "print", so that it doesn't pollute the list of variables that the user does want to interact with. > So why making it unnecessarily complicated? Hidden variables aren't complicated. I think the idea is elegant and useful. > But seriously: if youy write in the docs: Don't mess with variable > XXX, and they do, is their fault in exactly the same way like when > they mess with the source code. Where's the difference? Again, this is a user interface issue. Why expose a variable to a user that he shouldn't touch and can't use? -- Timur Tabi Linux Kernel Developer @ Freescale