unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "scopeview ." <scopeview126@gmail.com>
To: emacs-devel@gnu.org
Subject: What's the best way to write complex emacs extension
Date: Sun, 2 Nov 2014 07:25:27 +0800	[thread overview]
Message-ID: <CANOM=vdiXTDrnBLi=MLMdZnvWj4G1C6EFMd3j_57WV1JJPCMHA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

Hi all,

When I wrote my simple extension, pure elisp code is ok. But I found it is
hard to write complex elisp extension. Because when elisp predication
failed (for example stringp) it hard to find out the failed predication
place. (no file:function:line_number or backtrace)

So my complex extension is elisp + c++ code and I make elisp as simple
as possible. We can link c code to emacs binary, but I don't think it's a
good solution. In xemacs, we can extend elisp by writing c/c++ shared
library and load it dynamicly. If emacs has this feature, my complex emacs
extension can be much simpler.

Does there any other good way to extend emacs?
How about other emacs-alike editor like Hemlock written in common lisp
which can use many mature and complex common lisp library? Does anybody use
it?
I think xemacs's c/c++ shared library is more suitable. But it seems that
xemacs had stop its development.


following link is a simple extension of mine
http://www.emacswiki.org/emacs/dir-list

[-- Attachment #2: Type: text/html, Size: 1135 bytes --]

             reply	other threads:[~2014-11-01 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 23:25 scopeview . [this message]
2014-11-02  4:12 ` What's the best way to write complex emacs extension Stephen J. Turnbull
2014-11-02  5:27 ` Stefan Monnier
2014-11-04  0:16   ` scopeview .
2014-11-04  2:59     ` Alexis
2014-11-02 11:52 ` Stephen Leake

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='CANOM=vdiXTDrnBLi=MLMdZnvWj4G1C6EFMd3j_57WV1JJPCMHA@mail.gmail.com' \
    --to=scopeview126@gmail.com \
    --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).