From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Turning Gnus groups into real objects
Date: Fri, 19 Jul 2019 16:56:57 -0700 [thread overview]
Message-ID: <87lfwt60ja.fsf@ericabrahamsen.net> (raw)
In-Reply-To: jwvftn1u1ny.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> (defclass gnus-server ()
>> ((address :type string)
>> ...))
>>
>> (defclass gnus-nnimap (gnus-server)
>> ((capabilities
>> :type string)
>> (newlinep
>> :type boolean)
>> ...))
>
> Aka
>
> (cl-defstruct (gnus-server)
> (address nil :type string))
>
> (cl-defstruct (gnus-nnimap
> (:include gnus-server))
> (capabilities nil :type string)
> (newlinep nil :type boolean))
>
>> (cl-defmethod gnus-request-list ((server gnus-nnimap))
Aw... I was also considering a bit of (tastefully designed) multiple
inheritance.
> BTW, I was wondering whether we could preserve backward compatiblity with
> defvoo and defffoo. But I guess for `defvoo`, we'd need the equivalent
> of `define-symbol-macro` whereas we currently only have `cl-symbol-macrolet`.
That would be an interesting thing to have for many reasons. But here it
seems like it would mainly be useful to support backends defined outside
of Gnus, in which case we'd also have to cover `nnoo-declare' and
friends, and... yuck.
next prev parent reply other threads:[~2019-07-19 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 19:29 Turning Gnus groups into real objects Eric Abrahamsen
2019-07-17 21:33 ` Andy Moreton
2019-07-17 22:04 ` Eric Abrahamsen
2019-07-17 21:59 ` Stefan Monnier
2019-07-17 22:08 ` Eric Abrahamsen
2019-07-18 11:59 ` Lars Ingebrigtsen
2019-07-18 18:01 ` Eric Abrahamsen
2019-07-19 12:56 ` Lars Ingebrigtsen
2019-07-19 18:47 ` Eric Abrahamsen
2019-07-19 22:10 ` Stefan Monnier
2019-07-19 23:56 ` Eric Abrahamsen [this message]
2019-07-20 12:52 ` Lars Ingebrigtsen
2019-07-21 1:41 ` Eric Abrahamsen
2019-07-21 12:34 ` Barry Fishman
2019-07-22 17:14 ` Eric Abrahamsen
2019-07-21 13:40 ` Stefan Monnier
2019-07-22 16:38 ` Eric Abrahamsen
2019-07-21 14:02 ` Lars Ingebrigtsen
2019-07-22 16:26 ` 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
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=87lfwt60ja.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).