all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 25294@debbugs.gnu.org
Subject: bug#25294: 26.0.50; Allow more catch-all values for cl-defmethod's &context plus major-mode specializer
Date: Wed, 13 Dec 2017 16:06:39 -0800	[thread overview]
Message-ID: <87r2ry6uls.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lgi7cxcn.fsf@users.sourceforge.net> (Noam Postavsky's message of "Tue, 12 Dec 2017 18:58:32 -0500")

Noam Postavsky <npostavs@users.sourceforge.net> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> +Generic functions provide a new argument-list keyword,
>
> The way you phrased this might lead me to think that the &context
> keyword should go in the cl-defgeneric form (maybe it's not so bad when
> seeing in context under cl-defmethod, in patch form it's a bit
> disconnected).

Maybe so, yes. I'll look at it in context and see if I can't make that a
little clearer.

>> +@code{&context}, which can be used to introduce extra specializers
>> +that test the general environment in which the method is run.  This
>> +keyword should appear after the list of required arguments, but before
>> +any @code{&rest} or @code{&optional} keywords.
>
> I wonder if it would be clearer to add this to the @defmac header?
>
>     @defmac cl-defmethod name [qualifier] arguments [&context (expr spec)@dots{}] &rest [docstring] body
>
> Hmm, maybe that ends up being too long.

I never found those things very helpful, and that does look a little long...





  reply	other threads:[~2017-12-14  0:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 19:13 bug#25294: 26.0.50; Allow more catch-all values for cl-defmethod's &context plus major-mode specializer Eric Abrahamsen
2016-12-30  4:35 ` npostavs
2017-12-11 23:57   ` Eric Abrahamsen
2017-12-12  0:08     ` Noam Postavsky
2017-12-12  1:39 ` Noam Postavsky
2017-12-12  1:43   ` Noam Postavsky
2017-12-12  5:42   ` Eric Abrahamsen
2017-12-12 23:58     ` Noam Postavsky
2017-12-14  0:06       ` Eric Abrahamsen [this message]
2017-12-14 21:01       ` Eric Abrahamsen

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=87r2ry6uls.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=25294@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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.