unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@IRO.UMontreal.CA>,
	"'Bob Rogers'" <rogers-emacs@rgrjr.dyndns.org>,
	"'Leo'" <sdl.web@gmail.com>
Cc: 'emacs-devel' <emacs-devel@gnu.org>
Subject: RE: Elisp implementation of list-processes (and: Why islist-processes implemented in C?)
Date: Tue, 30 Nov 2010 20:16:02 -0800	[thread overview]
Message-ID: <0F845B134096442E89A45F2216664F52@us.oracle.com> (raw)
In-Reply-To: <jwvr5e2v8b4.fsf-monnier+emacs@gnu.org>

> It should probably go into subr.el.  Yes, it's a large file, 
> but that's not really a problem.  The only real problem with
> it is that this file can't use CL macros (because CL macros
> use functions defined in subr.el).

What about breaking out those functions used by CL macros into their own file?
That way other stuff in the file can use CL macros.  Otherwise it seems like
you're working with a pretty artificial limitation.

(Are those functions used _only_ by CL macros?  I'd guess not, otherwise we
would already have put them in their own file with a `cl-' prefix.)




  parent reply	other threads:[~2010-12-01  4:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 18:52 Adding a hook to list-processes Bob Rogers
2010-11-27 19:43 ` Davis Herring
2010-11-27 20:25   ` Bob Rogers
2010-11-28 18:49 ` Stefan Monnier
2010-11-28 18:54   ` Bob Rogers
2010-11-30  6:05   ` Elisp implementation of list-processes Bob Rogers
2010-11-30 21:06     ` Elisp implementation of list-processes (and: Why is list-processes implemented in C?) Stefan Monnier
2010-12-01  3:27       ` Leo
2010-12-01  4:16       ` Drew Adams [this message]
2010-12-01 10:55     ` Elisp implementation of list-processes Leo
2010-12-01 11:12     ` Leo
2010-12-02  2:48       ` Bob Rogers
2010-12-01 21:12     ` Richard Stallman

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=0F845B134096442E89A45F2216664F52@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=rogers-emacs@rgrjr.dyndns.org \
    --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).