[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Command substitution with null bytes generates warning
From: |
Greg Wooledge |
Subject: |
Re: Command substitution with null bytes generates warning |
Date: |
Fri, 16 Sep 2016 08:55:30 -0400 |
User-agent: |
Mutt/1.4.2.3i |
On Thu, Sep 15, 2016 at 10:51:22PM -0700, Eric Pruitt wrote:
> Fix:
> Is this even an intentional change? I looked at some of the other
> internal_warning invocations, and they were commented out using "#if 0
> ...
> #endif."
In 4.4-beta2, I see them in subst.c and parse.y and y.tab.c. In subst.c
they are inside an "#if 1" block. In the other two, they are inside
"#if 0".
I do not understand the discrepancy, but I would assume Chet made the
change intentionally. It seems unlikely to be something one would do
accidentally.
- Command substitution with null bytes generates warning, Eric Pruitt, 2016/09/16
- Re: Command substitution with null bytes generates warning,
Greg Wooledge <=
- Re: Command substitution with null bytes generates warning, Chet Ramey, 2016/09/17
- Re: Command substitution with null bytes generates warning, L. A. Walsh, 2016/09/19
- Re: Command substitution with null bytes generates warning, Greg Wooledge, 2016/09/19
- Re: Command substitution with null bytes generates warning, L. A. Walsh, 2016/09/19
- Re: Command substitution with null bytes generates warning, Eric Blake, 2016/09/19
- Re: Command substitution with null bytes generates warning, Linda Walsh, 2016/09/19
- Re: Command substitution with null bytes generates warning, Greg Wooledge, 2016/09/19
- Re: Command substitution with null bytes generates warning, Linda Walsh, 2016/09/19
- Re: Command substitution with null bytes generates warning, Chet Ramey, 2016/09/19
- Re: Command substitution with null bytes generates warning, L. A. Walsh, 2016/09/19