From: John Wiegley <jwiegley@gmail.com>
To: 22291@debbugs.gnu.org
Subject: bug#22291: 25.1.50; REGRESSION: Emacs 24.3 breaks loading cl-macs to get macro `case'
Date: Sun, 03 Jan 2016 13:31:28 -0800 [thread overview]
Message-ID: <m21t9yqrin.fsf@newartisans.com> (raw)
In-Reply-To: <837fjrc1v7.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 02 Jan 2016 19:44:44 +0200")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> Personally I tend to require `cl', and at compile-time only, to get
>> such macros. But it is entirely reasonable that someone might require
>> `cl-macs' - at runtime or compile time - to get such a macro definition.
>>
>> And if some user does not compile the code that requires the library
>> that provides the macro, then s?he will now get the entire `cl' at
>> runtime, instead of getting only the much-smaller `cl-macs' at runtime.
>>
>> > OK?
>>
>> Not IMHO.
> So I guess we will have to agree to disagree on this one.
> From my POV, this is not a bug, but a deliberate change that is well
> documented.
From the point of view of the bug report, I agree with Eli.
From the point of view of the issue, I agree with Drew. Drew, let's close this
as a bug, but open a new discussion on better organization of the CL stuff. We
should start the discussion on tangents, until we arrive at something
meaningful to bring to the developer's list.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-01-03 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<61b4ebe0-446c-49df-b5d1-c527a47192b5@default>
[not found] ` <<83a8oocr7i.fsf@gnu.org>
2016-01-02 17:28 ` bug#22291: 25.1.50; REGRESSION: Emacs 24.3 breaks loading cl-macs to get macro `case' Drew Adams
2016-01-02 17:44 ` Eli Zaretskii
2016-01-03 21:31 ` John Wiegley [this message]
2016-01-02 3:23 Drew Adams
2016-01-02 8:37 ` Eli Zaretskii
2016-01-02 17:50 ` bug#22291: 25.1.50; NOTABUG: " Glenn Morris
2016-01-02 18:16 ` Drew Adams
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=m21t9yqrin.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=22291@debbugs.gnu.org \
/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.