From: joakim@verona.se
To: Leo Liu <sdl.web@gmail.com>
Cc: "Eric M. Ludlam" <eric@siege-engine.com>,
emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
John Yates <john@yates-sheets.org>,
Jorgen Schaefer <forcer@forcix.cx>
Subject: Re: A unified project root interface
Date: Wed, 20 Mar 2013 08:04:23 +0100 [thread overview]
Message-ID: <m3ip4my2ko.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <m1li9ir81r.fsf@gmail.com> (Leo Liu's message of "Wed, 20 Mar 2013 12:48:00 +0800")
Leo Liu <sdl.web@gmail.com> writes:
> On 2013-03-20 11:21 +0800, Stefan Monnier wrote:
>> Right, preloading EIEIO is not what I was planning to do, indeed.
>> IOW, I think the challenge is to extract the "project-root" part of EDE
>> in such a way that it doesn't require preloading as much code.
>> That might require splitting EIEIO, or some other approach, maybe,
>> I don't know.
>
> I personally would like a package not using any of pseudo-CLOS features
> unless it is ABSOLUTELY necessary. There are projects with far larger
> scale and beautifully built before EIEIO came along.
Just so another view is represented then:
I think EIEIO is pretty neat. The EDE feature is also prety neat. It has
most features you need in a project root fromework already. What it
lacks is ease of use.
If we rewrite EDE using some other method, it will eventually turn into
EDE if its going to cater for the same use-cases.
IMHO if one would like to work on reducing the footprint of Emacs, which
is a worthy goal, greater gains could be made implementing lazy loading
of C libraries on platforms where its possible.
> Leo
>
--
Joakim Verona
next prev parent reply other threads:[~2013-03-20 7:04 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 16:44 A unified project root interface Jorgen Schaefer
2013-03-09 17:12 ` Fabian Ezequiel Gallina
2013-03-10 5:38 ` Stefan Monnier
2013-03-10 10:06 ` Jorgen Schaefer
2013-03-11 18:57 ` Lluís
2013-03-12 23:28 ` Eric M. Ludlam
2013-03-12 23:42 ` Jorgen Schaefer
2013-03-13 2:02 ` Eric M. Ludlam
2013-03-13 18:03 ` David Engster
2013-03-13 19:11 ` Sudish Joseph
2013-03-16 0:47 ` Eric M. Ludlam
2013-03-16 14:18 ` David Engster
2013-03-16 15:02 ` Jorgen Schaefer
2013-03-16 22:27 ` Phil Hagelberg
2013-03-16 22:59 ` David Engster
2013-03-16 23:16 ` Jorgen Schaefer
2013-03-17 17:40 ` David Engster
2013-03-17 18:18 ` Jorgen Schaefer
2013-03-18 22:50 ` David Engster
2013-03-19 1:57 ` John Yates
2013-03-19 7:18 ` David Engster
2013-03-19 12:23 ` Eric M. Ludlam
2013-03-19 13:06 ` Stefan Monnier
2013-03-19 19:09 ` David Engster
2013-03-20 3:21 ` Stefan Monnier
2013-03-20 4:48 ` Leo Liu
2013-03-20 7:04 ` joakim [this message]
2013-03-20 7:05 ` David Engster
2013-03-20 7:13 ` David Engster
2013-03-20 12:57 ` Stefan Monnier
2013-03-20 16:14 ` Davis Herring
2013-03-20 17:41 ` Stefan Monnier
2013-03-20 17:48 ` Stefan Monnier
2013-03-20 18:20 ` Bruce Korb
2013-03-20 22:14 ` Stefan Monnier
2013-03-20 16:34 ` David Engster
2013-03-20 17:47 ` Stefan Monnier
2013-03-21 0:55 ` Eric M. Ludlam
2013-03-21 3:27 ` Stefan Monnier
2013-03-21 4:07 ` Eric M. Ludlam
2013-03-21 14:33 ` Stefan Monnier
2013-03-22 2:12 ` Eric M. Ludlam
2013-03-23 11:04 ` EIEIO split (was: A unified project root interface) David Engster
2013-03-21 16:32 ` A unified project root interface David Engster
2013-03-22 0:47 ` Eric M. Ludlam
2013-03-22 20:30 ` David Engster
2013-03-23 17:10 ` Eric M. Ludlam
2013-03-23 17:26 ` Jorgen Schaefer
2013-03-23 18:02 ` Dmitry Gutov
2013-03-23 20:51 ` Pascal J. Bourguignon
2013-03-24 4:25 ` Dmitry Gutov
2013-03-24 10:13 ` Jorgen Schaefer
2013-04-06 13:25 ` Jorgen Schaefer
2013-04-06 17:13 ` Eric M. Ludlam
2013-04-08 19:03 ` David Engster
2013-12-31 20:12 ` Daniel Colascione
2013-03-20 17:49 ` Jorgen Schaefer
2013-03-19 7:33 ` Jorgen Schaefer
2013-03-17 8:08 ` joakim
2013-03-12 15:34 ` Sudish Joseph
2013-03-12 16:51 ` Dmitry Gutov
2013-03-12 18:23 ` Ted Zlatanov
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=m3ip4my2ko.fsf@chopper.vpn.verona.se \
--to=joakim@verona.se \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
--cc=forcer@forcix.cx \
--cc=john@yates-sheets.org \
--cc=monnier@iro.umontreal.ca \
--cc=sdl.web@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 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).