Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15122 > unrolled thread

Re: alias problem -- conflict found

Started byGreg Wooledge <wooledg@eeg.ccf.org>
First post2019-07-10 11:54 -0400
Last post2019-07-10 11:54 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: alias problem -- conflict found Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-10 11:54 -0400

#15122 — Re: alias problem -- conflict found

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-07-10 11:54 -0400
SubjectRe: alias problem -- conflict found
Message-ID<mailman.848.1562774074.2688.bug-bash@gnu.org>
On Wed, Jul 10, 2019 at 10:29:14PM +0700, Robert Elz wrote:
>     From:        L A Walsh <bash@tlinx.org>
>   | Functions can't process their arguments in the current scope.
> 
> I have no idea what you're getting at there.

She wants something like Tcl's [uplevel] command, most likely.

http://www.tcl.tk/man/tcl8.6/TclCmd/uplevel.htm

Short version: evaluate a command in the caller's scope, instead of in
the function's scope.  In Tcl, you can use this (WITH EXTREME CAUTION)
to implement new commands with the semantic powers of "if" or "for".
It makes "eval" look like a toy.

Bash has nothing like this.  Bash doesn't even come CLOSE to this.
It was never designed for this.  It's a SHELL.  If she's using aliases
to try to mimic this behavior, I have nothing more to say on this topic.
Horse, beating.

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web