On Wed, Aug 19, 2015 at 08:39:15AM +, Craig wrote:
> It's somewhat cumbersome to have to transport this assert function from
> project to project, so it would save a considerable amount of effort and
> time if it were built-in.
> function assert() {
> local lineno=${BASH_LINENO[0]} \
>
Is this the appropriate place to present feature requests or is there
another forum for that?
I am keen to propose the introduction of an assert built-in. The only
purpose of this built-in is to behave functionally identical to the eval
built-in, except that on error, the current shell process ex
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
On 18 Aug 2015 21:41, Linda Walsh wrote:
> Mike Frysinger wrote:
> > On 18 Aug 2015 13:34, Linda Walsh wrote:
> > (2) it's using the nss system which lets people drop modules into the system
> > at anytime and change the overall lookups to use that. statically linking a
> > specific subset would b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/18/15 11:41 PM, Mike Frysinger wrote:
> just to double check, the warning from this code is expected ?
>
> $ bash-4.3 -c 'declare -a foo=(a b c); export foo; declare -p foo'
> declare -ax foo='([0]="a" [1]="b" [2]="c")'
> $ bash-4.4 -c "declare
