From: Glenn Morris <rgm@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: trunk r117534: Unbreak compilation of derived cc-mode modes
Date: Tue, 15 Jul 2014 02:00:14 -0400 [thread overview]
Message-ID: <grr41nf9g1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <53C4A871.8030702@dancol.org> (Daniel Colascione's message of "Mon, 14 Jul 2014 21:05:05 -0700")
Daniel Colascione wrote:
>> Why is this needed, when cc-defs requires cl at compile time,
>> which defines cl-macroexpand-all as an alias for macroexpand-all?
>
> I was trying to fix some code that broke when requiring cc-langs and
> cc-fonts only. Requiring these features doesn't bring the needed alias,
> but apparently used to:
>
> ELISP> (require 'cc-langs)
> cc-langs
> ELISP> (require 'cc-fonts)
> cc-fonts
> ELISP> (featurep 'cl)
> nil
>
> Maybe that's the real bug.
Doesn't whether that's "right" or not depend on whether you are loading
the compiled or uncompiled versions? cc-mode was certainly not
_supposed_ to be loading cl (or cc-langs) at runtime when run compiled,
though for a time it did:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17463
I can't say I understand all this cc-mode stuff, but I made the change
from cl to cl-lib in emacs-24, so if something needs fixing it
probably needs fixing there too.
next prev parent reply other threads:[~2014-07-15 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1X6q9D-0003AI-D2@vcs.savannah.gnu.org>
2014-07-15 3:47 ` trunk r117534: Unbreak compilation of derived cc-mode modes Glenn Morris
2014-07-15 4:05 ` Daniel Colascione
2014-07-15 6:00 ` Glenn Morris [this message]
2014-07-15 6:19 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=grr41nf9g1.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).