>
> 1. I noticed bash variables don't support null characters (0x00). This is
> unlike
> perl and other languages. Will this ever change? Have people requested or
> wanted
> this feature?
POSIX says that the use of NUL bytes gives undefined behavior in a shell.
zsh supports this, but it would
Hi,
This command takes about 2 seconds to complete (on a slow machine; you can
make it a triple loop for a faster machine):
foo=`rm -f empty; touch empty; \
for a in 0 1 2 3 4 5 6 7 8 9 ; do \
for b in 0 1 2 3 4 5 6 7 8 9 ; do \
echo g$a$b | cat; \
done; \
done |
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
bug-bash,
I have a few issues to address, that I arrived at recently. None of them are
necessarily bugs.
1. I noticed bash variables don't support null characters (0x00). This is
unlike perl and other languages. Will this ever change? Have people requested
or wanted this feature?
2. $(
