From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Davis Herring Newsgroups: gmane.emacs.devel Subject: Re: Emacs 25.0.94: Is require failing to define macros and functions at compile time? Date: Wed, 29 Jun 2016 13:06:53 -0600 Organization: XCP-1 Message-ID: <57741C4D.6070103@lanl.gov> References: <5773E5D6.8040201@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1467229328 957 80.91.229.3 (29 Jun 2016 19:42:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Jun 2016 19:42:08 +0000 (UTC) Cc: =?UTF-8?Q?Cl=c3=a9ment_Pit--Claudel?= , emacs-devel To: rswgnu@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 29 21:42:00 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bILN1-0004RM-UY for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2016 21:42:00 +0200 Original-Received: from localhost ([::1]:45520 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bILMx-0003dv-Vq for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2016 15:41:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bILMR-0003cP-NG for emacs-devel@gnu.org; Wed, 29 Jun 2016 15:41:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bILMO-0002o2-JV for emacs-devel@gnu.org; Wed, 29 Jun 2016 15:41:23 -0400 Original-Received: from proofpoint4.lanl.gov ([2001:400:4210:400::a4]:57653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bILMO-0002nx-7z for emacs-devel@gnu.org; Wed, 29 Jun 2016 15:41:20 -0400 Original-Received: from mailrelay1.lanl.gov (mailrelay1.lanl.gov [128.165.4.101]) by mailgate4.lanl.gov (8.15.0.59/8.15.0.59) with ESMTP id u5TJ6s2d007228; Wed, 29 Jun 2016 13:06:54 -0600 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by mailrelay1.lanl.gov (Postfix) with ESMTP id 1FBC71402C13; Wed, 29 Jun 2016 13:06:54 -0600 (MDT) X-NIE-2-Virus-Scanner: amavisd-new at mailrelay1.lanl.gov Original-Received: from chinstrap.lanl.gov (chinstrap.lanl.gov [128.165.123.246]) by mailrelay1.lanl.gov (Postfix) with ESMTP id 05C501402C11; Wed, 29 Jun 2016 13:06:53 -0600 (MDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 In-Reply-To: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.96, 1.0.3, 0.0.0000 definitions=2016-06-29_10:2016-06-29, 2016-06-29, 1970-01-01 signatures=0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] X-Received-From: 2001:400:4210:400::a4 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:204943 Archived-At: > So maybe the byte-compiler could be made smarter to handle a list of > requires. If a library has 10 requires, why should we have to write > out require 10 times or add the eval-and-compile call? Maybe there is > a need for a require-list primitive for such circumstances so that it > is always available at compilation time. Any library complicated enough to have N `require's will by necessity have so many more lines of code than N that the longhand list of (require 'foo) will be negligible. Doing it the simple(minded), obvious way has the advantage that it makes trivial things like grep easier. Obviously it is a complexity that the meaning of `require' depends on whether you're compiling or not; the above is simply a statement about practicalities. Davis -- This product is sold by volume, not by mass. If it appears too dense or too sparse, it is because mass-energy conversion has occurred during shipping.