From: David Engster <deng@randomsample.de>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: Jonas Bernoulli <jonas@bernoul.li>, 16998@debbugs.gnu.org
Subject: bug#16998: with-slots should expand to cl-symbol-macrolet
Date: Wed, 12 Mar 2014 23:52:59 +0100 [thread overview]
Message-ID: <87eh273u7o.fsf@engster.org> (raw)
In-Reply-To: <5320DBE6.3020706@siege-engine.com> (Eric M. Ludlam's message of "Wed, 12 Mar 2014 18:12:54 -0400")
Eric M. Ludlam writes:
> On 03/12/2014 02:00 PM, David Engster wrote:
>> However, I think that there's no problem to "officially" state that
>> EIEIO development now happens in Emacs, and that the version in CEDET
>> will not get updated anymore, but will remain there as a fallback
>> library for older Emacsen (similar to what Gnus does).
>>
>> Eric, would you be OK with that? That would allow us to update the
>> built-in EIEIO to current Emacs coding standards without breaking
>> CEDET-from-bzr on older Emacsen.
>
> This proposal is fine by me. Short term we will just need to find a
> good way to have standalone CEDET bootstrap in with either the Emacs
> version, or with the one in CEDET.
Yes. I'd move EIEIO upstream in some 'fallback-libs' directory or
similar, and put this in load-path when Emacs version is <23.4 during
compilation as well as when CEDET is loaded.
> Eventually this will become unnecessary.
Yes. Our minimum version currently is 23.2, and as long as it does not
become too painful, there's no need to bump it.
> The CEDET bootstrapping still cares about some features missing from
> Emacs (according to the comments) such as:
>
> ;; Currently, Emacs proper doesn't track EIEIO methods. Until it
> ;; does, we have to advice `describe-variable' and `describe-function'
> ;; for EIEIO methods to get better help buffers.
>
> and
>
> ;; This adds further formatting and hyperlinks.
> (add-hook 'temp-buffer-show-hook 'eieio-help-mode-augmentation-maybee t)
Actually, that feature will be part of the upcoming 24.4 release, so it
won't be needed there.
> I think we will just need to check the Emacs version, and change how
> we bootstrap and compile. I'm interested in any advice on this.
I don't think this should be too difficult, but if it turns out to be a
nightmare, I think we could bump the minimum version to 23.4 without
alienating too many people...
-David
next prev parent reply other threads:[~2014-03-12 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 14:22 bug#16998: with-slots should expand to cl-symbol-macrolet Jonas Bernoulli
2014-03-12 15:12 ` Juanma Barranquero
2014-03-12 15:35 ` Stefan Monnier
2014-03-12 16:04 ` Juanma Barranquero
2014-03-12 18:00 ` David Engster
2014-03-12 18:46 ` Stefan Monnier
2014-03-12 22:12 ` Eric M. Ludlam
2014-03-12 22:52 ` David Engster [this message]
2020-08-16 18:57 ` Jonas Bernoulli
2020-08-16 19:09 ` Lars Ingebrigtsen
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=87eh273u7o.fsf@engster.org \
--to=deng@randomsample.de \
--cc=16998@debbugs.gnu.org \
--cc=eric@siege-engine.com \
--cc=jonas@bernoul.li \
/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).