From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Jason Rumney <jasonr@gnu.org>
Cc: schwab@linux-m68k.org, 10783@debbugs.gnu.org
Subject: bug#10783: Some built-in functionslost their argument names
Date: Mon, 13 Feb 2012 10:19:34 -0500 [thread overview]
Message-ID: <jwvehtyydfs.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <871upydg5x.fsf@gnu.org> (Jason Rumney's message of "Mon, 13 Feb 2012 21:19:38 +0800")
>> Just for the record: such duplicate definitions should be removed.
>> E.g. the C and pc-win.el definitions should be refactored such that
>> there is only one C definition (which might call an Elisp implementation
>> in the MS-DOS case).
> Wouldn't it be better for the common definition to be Lisp, with calls
> into C where necessary?
Depends on the actual code in the common part. It will have some kind
of dispatch to the appropriate backend, which can either go through the
terminal methods or through some case/switch. In the case we use
case/switch it can just as well be performed in Elisp, indeed.
But the common code may also include more shared code which may require
the use of C, or in some other cases we won't want to expose the
backend-specific code to Elisp.
Stefan
PS: Of course, the common code should not use the "x-" prefix.
next prev parent reply other threads:[~2012-02-13 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 21:25 bug#10783: Some built-in functionslost their argument names Glenn Morris
2012-02-10 23:04 ` Andreas Schwab
2012-02-10 23:30 ` Glenn Morris
2012-02-11 7:43 ` Andreas Schwab
2012-02-11 9:54 ` Eli Zaretskii
2012-02-11 10:01 ` Eli Zaretskii
2012-02-11 22:40 ` Glenn Morris
2012-02-12 3:23 ` Glenn Morris
2012-02-12 4:05 ` Eli Zaretskii
2012-02-12 5:14 ` Glenn Morris
2012-02-12 16:30 ` Eli Zaretskii
2012-03-06 19:50 ` Glenn Morris
2012-02-12 4:02 ` Eli Zaretskii
2012-02-12 15:28 ` Stefan Monnier
2012-02-12 16:29 ` Eli Zaretskii
2012-02-12 17:01 ` Stefan Monnier
2012-02-12 19:53 ` Glenn Morris
2012-02-13 13:19 ` Jason Rumney
2012-02-13 15:19 ` Stefan Monnier [this message]
2012-02-12 19:58 ` 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=jwvehtyydfs.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=10783@debbugs.gnu.org \
--cc=jasonr@gnu.org \
--cc=schwab@linux-m68k.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).