public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] simplify bootm command
Date: Tue, 05 Aug 2008 13:05:11 +0200	[thread overview]
Message-ID: <20080805110511.47ACF24851@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 05 Aug 2008 06:38:37 EDT." <48982DAD.2060408@gmail.com>

In message <48982DAD.2060408@gmail.com> you wrote:
>
> That would be REALLY cool!  It would take some initial work, but the 
> reward would be really simple and transparent expandability for the 
> command set.  As with the "bootm" command, we might end up with simpler 
> code (I don't think too many commands are as bad as bootm, however).

:-)

> One minor flaw, I don't see how "bootm" the env script could run "bootm" 
> the built-in command, because it would instead recursively run "bootm" 
> the env script if scripts have higher priority and the command line 
> "bootm" would run the built-in "bootm" if scripts have lower priority. 

That's why I think we should have an explicit "builtin" command, i. e.
command with the name "builtin" that will always run the corresponding
builtin command, no if there is a "command alias" or not - similar to
the bash command:

       builtin shell-builtin [arguments]
              Execute the specified shell builtin, passing it
              arguments, and return its exit status. This is useful
              when defining a function whose name is the same as a
              shell builtin, retaining the functionality of the
              builtin within the function. The cd builtin is commonly
              redefined this way. The return status is false if
              shell-builtin is not a shell builtin command.

> The way I see it, env scripts should have higher priority than built-in 
> commands and would supercede the built-in.  Hmm, one possible way out of 
> the dilemma would be to support quoting built-in commands to force them, 
> rather than the env script: `bootm` would be the built-in command (just 
> as a concept, I don't know how back-tick quoting would conflict with 
> existing hush parsing).

I don't like to use quoting (of  any  kind)  for  this  because  this
already  has  certain  meaning in the shell. Also, this would be more
effort to implement that the "builtin" command I suggested.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Vulcans believe peace should not depend on force.
	-- Amanda, "Journey to Babel", stardate 3842.3

  reply	other threads:[~2008-08-05 11:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05  3:51 [U-Boot-Users] simplify bootm command Kumar Gala
2008-08-05 10:02 ` Jerry Van Baren
2008-08-05 10:19   ` Wolfgang Denk
2008-08-05 10:38     ` Jerry Van Baren
2008-08-05 11:05       ` Wolfgang Denk [this message]
2008-08-05 11:16         ` Albert ARIBAUD
2008-08-05 13:01           ` Wolfgang Denk
2008-08-05 13:45             ` Albert ARIBAUD
2008-08-05 12:15         ` Jerry Van Baren
2008-08-05 13:59           ` Detlev Zundel
2008-08-05 12:56     ` Kumar Gala
2008-08-05 13:36       ` Jerry Van Baren
2008-08-05 13:59         ` Kumar Gala
2008-08-05 14:08         ` Wolfgang Denk
2008-08-05 14:32           ` [U-Boot-Users] simplify bootm command -- deprecated or removing functionality? Kumar Gala
2008-08-05 14:45             ` Wolfgang Denk
2008-08-05 14:48               ` Kumar Gala
2008-08-05 15:05         ` [U-Boot-Users] simplify bootm command Kumar Gala
2008-08-05 16:11           ` Jerry Van Baren
2008-08-05 16:27             ` Kumar Gala

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=20080805110511.47ACF24851@gemini.denx.de \
    --to=wd@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox