[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sr #110655] AT&T UnixPC (3b1) shell thrown off by #( after case.

From: Alain Knaff
Subject: [sr #110655] AT&T UnixPC (3b1) shell thrown off by #( after case.
Date: Thu, 26 May 2022 18:05:35 -0400 (EDT)

Follow-up Comment #6, sr #110655 (project autoconf):

[comment #4 comment #4:]
> That said, the observation that even current shells will choke on `eval` of
shell variables containing long runs of shell code including comments, is
valuable.  That's something we should be avoiding in general and not just in
this case.
> (We should be trying to move away from shell variables containing shell
code, period.  That's what shell functions are for.)

Indeed. There is one remaining case of this in _AC_INIT_PREPARE, which sets up
a trap to be run on exit (after line 1315 of
/usr/share/autoconf/autoconf/general.m4). The trap is a huge string of shell
code. IMHO, the bulk of this should be in a function, to be called by a much
smaller trap. I'm also getting the impression that this causes problems on low
memory machines.


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]