Re: Processing of convenience variables for scripts ...

[Daniel Jacobowitz <drow@mvista.com>]

On Fri, Dec 06, 2002 at 05:53:31PM -0500, Fernando Nasser wrote:
> Richard Sharpe wrote:> On Fri, 6 Dec 2002, Fernando Nasser wrote:
> >
> >
> >>Daniel Jacobowitz wrote:
> >>
> >>>That said, I'm not worried about implementing this as much as I am
> >>>designing what it "ought" to look like.
> >>>
> >>
> >>For me just:
> >>
> >>eval command args... ${something} more args...
> >>
> >>where the value of ${something} is blah
> >>
> >>causes the following command to be executed
> >>
> >>command args... blahh more args...
> >>
> >>
> >>eval just expands the variable to create the real command to be excuted 
> >>and calls execute_command() with it.
> >
> >
> >This sounds like a simple short-term solution while we wait on a more 
> >general method where all commands can take expressions of any type :-)
> >
> 
> Why we would want that?  Are you thinking of any specific example where 
> this could be useful?

Well, it seems much more logical to me... right now some commands
accept $var and some don't.  The inconsistency gets on my nerves when I
hit it.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer