Re: Is there a way to not to ignore null in $()?

[Eli Schwartz]

On 5/11/20 8:13 AM, Peng Yu wrote:
> $ x=$(awk -e 'BEGIN{print "a\000b" }')
> -bash: warning: command substitution: ignored null byte in input
> $ declare -p x
> declare -- x="ab"
> 
> I think that there is no way to avoid the above warning as no null
> character can be in a bash variable. But if I want to avoid using a
> temp file, then I have to have to save the output in a bash variable?
> 
> Is there a good way to save some binary data in memory in bash? Thanks.

The warning is literally telling you that you cannot store null bytes in
bash, and it is ignoring it.

The warning is relatively new, it exists to alert you to the fact that
before then, those null bytes were always ignored, but were ignored
silently.

Please rewrite your application in a real programming language, which
can store arbitrary data like null bytes.

Or use a temp file/pipe. Stop trying to ignore literally the only
solution because you don't like it. Why is it that essentially every one
of your posts to this list is "bash is telling me I am not permitted to
do XXX, is there a way to do it anyway"?

-- 
Eli Schwartz
Bug Wrangler and Trusted User

signature.asc
Description: OpenPGP digital signature