Zack Weinberg wrote:
On Fri, Dec 15, 2023, at 7:08 PM, Jacob Bachmeyer wrote:
Zack Weinberg wrote:
[...]
Also, there’s a perl 2.14ism in one place (s///a) which I need
to figure out how to make 2.6-compatible before it can land.
...
+ $q_channel =~ s/([^\x20-\x7e])/"\\x".sp
On Fri, Dec 15, 2023, at 6:52 PM, Karl Berry wrote:
> Hi Zack,
>
> Since this touches code shared between Autoconf and Automake, I'm not
> checking it in yet and I'm requesting comments from both sides of the
> fence.
>
> Well, it seems good to me in principle, FWIW. I don't think this
On Fri, Dec 15, 2023, at 7:08 PM, Jacob Bachmeyer wrote:
> Zack Weinberg wrote:
>> [...]
>> Also, there’s a perl 2.14ism in one place (s///a) which I need
>> to figure out how to make 2.6-compatible before it can land.
...
>> + $q_channel =~ s/([^\x20-\x7e])/"\\x".sprintf("%02x", ord($1))/aeg;
...
Zack Weinberg wrote:
[...]
Since this touches code shared between Autoconf and Automake, I’m not
checking it in yet and I’m requesting comments from both sides of the
fence. Also, there’s a perl 2.14ism in one place (s///a) which I need
to figure out how to make 2.6-compatible before it can lan
Hi Zack,
Since this touches code shared between Autoconf and Automake, I'm not
checking it in yet and I'm requesting comments from both sides of the
fence.
Well, it seems good to me in principle, FWIW. I don't think this
directly affects automake? I admit I did not try to extract the
In autoconf 2.69, the manual said that you could use “all” and the
empty string as the first argument to m4_warn. As far as I can tell
this was never actually true, and the manual was corrected in 2.70,
but we still got a bug report from someone who tried it and got a
confusing internal error from
