[prev in list] [next in list] [prev in thread] [next in thread] 

List:       autoconf
Subject:    Re: config.sub/config.guess using nonportable $(...) substitutions
From:       Karl Berry <karl () freefriends ! org>
Date:       2021-03-09 19:09:00
Message-ID: 202103091909.129J90es010043 () freefriends ! org
[Download RAW message or body]

    At some point, failing to support $(...) is in the same ballpark 

FWIW, I fully disagree. (Along with, it seems, everyone else except
you and Ben.)

1) There is no actual benefit to using $(...) over `...`.
It is purely cosmetic. In other scripts, fine. In config.*, no.

2) Using $(...) causes a real-life problem on a real-life system.
Talking about # as an analogy is a red herring. # does not cause
real-life problem.

I just don't understand the overwhelming need to create this problem for
ourselves. -k

[prev in list] [next in list] [prev in thread] [next in thread]