all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nic Ferrier <nferrier@ferrier.me.uk>
To: emacs-devel@gnu.org
Subject: non-local exits with signal and condition-case
Date: Sun, 02 Jun 2013 17:24:47 +0100	[thread overview]
Message-ID: <87ip1wjx9s.fsf@ferrier.me.uk> (raw)

Is it just me or is catch annoying for some non-local exits?

When I do non-local exits, which isn't often, I mostly want to
non-locally exit and pass some data back.

Maybe this is the fault of my exposure to Java programming and using
exceptions for flow control? Anyway. I find that catch rarely fulfils my
needs.

It's possible to use signal and condition-case to achieve the effect
that I most often want and I do use them.

But making new signals is slightly annoying because you need to add 2
different properties to a symbol.

I propose a simple macro to make this easier:

 (defmacro defsignal (err-symbol inherits-list message)
   (let ((errv (make-symbol "err-v")))
     `(let ((,errv ,err-symbol))
        (put ,errv
             'error-conditions
             (quote ,inherits-list))
        (put ,errv
             'error-message
             ,message))))

One uses it like this:

 (defsignal :nictest-blah (:nictest :nictest-blah) "blah!")

I'm not sure where to put this. I could package it. But I'm collecting a
list of these things (noflet, let-while, etc...) and gradually it seems
I'm inventing my own lisp.

This one though seems to be a genuine gap in elisp.

Is there any interest in core-ing it?



Nic



             reply	other threads:[~2013-06-02 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02 16:24 Nic Ferrier [this message]
2013-06-02 18:52 ` non-local exits with signal and condition-case Stefan Monnier
2013-06-02 21:33   ` Nic Ferrier
2013-06-03  0:02     ` Stefan Monnier
2013-06-03 15:54     ` Davis Herring

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ip1wjx9s.fsf@ferrier.me.uk \
    --to=nferrier@ferrier.me.uk \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.