All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: hidden environment variables
Date: Mon, 23 Apr 2007 18:20:58 -0500	[thread overview]
Message-ID: <462D3F5A.1040307@freescale.com> (raw)
In-Reply-To: <20070423215158.808153535D2@atlas.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

  reply	other threads:[~2007-04-23 23:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 16:46 [U-Boot-Users] RFC: hidden environment variables Timur Tabi
2007-04-23 17:29 ` Grant Likely
2007-04-23 18:47 ` Ulf Samuelsson
2007-04-23 19:22 ` Wolfgang Denk
2007-04-23 20:28   ` Scott Wood
2007-04-23 21:51     ` Wolfgang Denk
2007-04-23 23:20       ` Timur Tabi [this message]
2007-04-24  0:12         ` Wolfgang Denk
2007-04-24 18:58           ` Rune Torgersen
2007-04-23 19:28 ` Ben Warren
2007-04-23 19:32   ` Ulf Samuelsson
2007-04-23 19:39     ` Ben Warren
2007-04-23 19:45       ` Timur Tabi
2007-04-23 19:53         ` Ben Warren
2007-04-23 21:49           ` Timur Tabi
2007-04-23 22:04             ` Ben Warren
2007-04-23 21:37         ` Wolfgang Denk
2007-04-23 21:56           ` Timur Tabi
2007-04-23 22:13             ` Wolfgang Denk
2007-04-23 23:19               ` Timur Tabi
2007-04-24  0:06                 ` Wolfgang Denk
2007-04-23 21:34     ` Wolfgang Denk
2007-04-24  9:05     ` Ladislav Michl
2007-04-23 19:49   ` Scott Wood
2007-04-23 21:40     ` Wolfgang Denk
2007-04-23 19:50   ` Timur Tabi
2007-04-23 20:05     ` Jeff Mann
2007-04-23 21:46       ` Wolfgang Denk
2007-04-23 21:51       ` Timur Tabi
2007-04-23 22:05         ` Wolfgang Denk
2007-04-23 23:14           ` Timur Tabi
2007-04-23 23:52             ` Wolfgang Denk
2007-04-24 13:43               ` Truong, Loc
2007-04-23 21:43     ` Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=462D3F5A.1040307@freescale.com \
    --to=timur@freescale.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.