Hi,
I noticed a little bug:
func()
{
echo "Inside the shell function, foo is $foo"
}
foo=foo
foo=bar func
echo "foo is now $foo"
will export foo=bar in global scope (i.e. it affects the execution environment
after the function call).
This is inconsistent with calls to commands (both bui
Hi,
Rudolf Polzer wrote:
> foo=bar func
> echo "foo is now $foo"
>
> will export foo=bar in global scope (i.e. it affects the execution environment
> after the function call).
[...]
> A shell function however isn't a "special built-in" and also counts as a
> "command name", thus the last echo lin
On Thu, Jul 14, 2011 at 04:26:16AM -0500, Jonathan Nieder wrote:
> Hi,
>
> Rudolf Polzer wrote:
>
> > foo=bar func
> > echo "foo is now $foo"
> >
> > will export foo=bar in global scope (i.e. it affects the execution
> > environment
> > after the function call).
> [...]
> > A shell function howe
Rudolf Polzer wrote:
> So basically - when using an assignment for the duration of a shell command
> execution, an explicit subshell must be used in portable scripts, as
> interpretation of this construct differs among shells and thus cannot be
> relied
> on.
If "shell command execution" means "
On Fri, Jul 08, 2011 at 10:05:38AM +, maximilian attems wrote:
> dash didn't compile in DEBUG mode against klibc for all long time.
> Now it only fails at link stage for not having setlinebuf(3) and
> freopen(3).
Applied. Thanks!
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~h
