all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: rswgnu@gmail.com
Cc: "Clément Pit--Claudel" <clement.pit@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: RE: Emacs 25.0.94: Is require failing to define macros and functions at compile time?
Date: Wed, 29 Jun 2016 13:59:40 -0700 (PDT)	[thread overview]
Message-ID: <3da5b37d-e607-45b1-aaab-ba71f53ba862@default> (raw)
In-Reply-To: <CA+OMD9iob=9mcxcrkuaBQnvExjdFTm19BEUm3f1N2W7NuniNZA@mail.gmail.com>

> On Wed, Jun 29, 2016 at 3:59 PM, Drew Adams <drew.adams@oracle.com> wrote:
>
> >> 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.

No, I didn't write that.  (But I did second it.)

> What happened to less code is easier to maintain?  Or don't repeat yourself?

Platitudinous abstraction.  Devil is in details.



  reply	other threads:[~2016-06-29 20:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 14:55 Emacs 25.0.94: Is require failing to define macros and functions at compile time? Robert Weiner
2016-06-29 15:14 ` Clément Pit--Claudel
2016-06-29 15:44   ` Robert Weiner
2016-06-29 19:06     ` Davis Herring
2016-06-29 19:59       ` Drew Adams
2016-06-29 20:34         ` Robert Weiner
2016-06-29 20:59           ` Drew Adams [this message]
2016-06-29 21:04           ` John Mastro
2016-06-30  0:09           ` Herring, Davis
2016-06-30  5:56             ` Robert Weiner
2016-06-29 15:16 ` Drew Adams
2016-06-29 22:03   ` Michael Heerdegen
2016-06-29 22:09     ` Robert Weiner
2016-06-29 22:27       ` Michael Heerdegen
2016-06-29 22:42         ` Drew Adams
2016-06-29 23:14           ` Robert Weiner
2016-06-29 22:07 ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3da5b37d-e607-45b1-aaab-ba71f53ba862@default \
    --to=drew.adams@oracle.com \
    --cc=clement.pit@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rswgnu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.