From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: CHECK_STRUCTS/dmpstruct.h mechanism is broken. Date: Sat, 13 Apr 2019 19:52:52 -0700 Organization: UCLA Computer Science Department Message-ID: References: <20190228202146.GC4686@ACM> <20190228205955.GD4686@ACM> <20190410162203.GA4009@ACM> <9809d5ce-c1c4-48e9-6dac-489431b34067@cs.ucla.edu> <671ba8dd-894b-5698-d162-8901b1098b9a@cs.ucla.edu> <83k1g04al8.fsf@gnu.org> <93b861b3-41d2-e590-d4b8-46a4bb64bfe8@cs.ucla.edu> <8736mmxr2e.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="264653"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 14 04:53:11 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hFVGZ-0016jS-49 for ged-emacs-devel@m.gmane.org; Sun, 14 Apr 2019 04:53:11 +0200 Original-Received: from localhost ([127.0.0.1]:58504 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hFVGT-0004rn-Gy for ged-emacs-devel@m.gmane.org; Sat, 13 Apr 2019 22:53:09 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:46782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hFVGK-0004rO-Hk for emacs-devel@gnu.org; Sat, 13 Apr 2019 22:52:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hFVGJ-00041u-Jq for emacs-devel@gnu.org; Sat, 13 Apr 2019 22:52:56 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:60394) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hFVGJ-00041Q-By for emacs-devel@gnu.org; Sat, 13 Apr 2019 22:52:55 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id D0086161515 for ; Sat, 13 Apr 2019 19:52:53 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id oqc5KjcXD_U3 for ; Sat, 13 Apr 2019 19:52:52 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id C88A31616ED for ; Sat, 13 Apr 2019 19:52:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rEhXMg-b3vyR for ; Sat, 13 Apr 2019 19:52:52 -0700 (PDT) Original-Received: from [192.168.1.9] (cpe-23-242-74-103.socal.res.rr.com [23.242.74.103]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id A34EF160A4B for ; Sat, 13 Apr 2019 19:52:52 -0700 (PDT) In-Reply-To: <8736mmxr2e.fsf@Rainer.invalid> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:235417 Archived-At: Achim Gratz wrote: > You'll end up re-implementing years and years of autoconf experience and > probably badly. The "years and years" of experience you're taking about is experience that is under my belt. I have been a reasonably major contributor to Autoconf and to all the Emacs configury code and I know how it works. I would not reimplement it badly. The idea I have is basically the idea that you proposed in another email: do the obvious parallelizations with the current recipes. However, doing this under the aegis of Autoconf would be a mistake. Autoconf is essentially unmaintained now, and for good reason: it's a dead-end and nobody wants to deal with it. We should be looking at migrating its good stuff (mostly shell+m4 recipes) to a better framework.