From: Eric Schulte <schulte.eric@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: EIEIO
Date: Fri, 14 Mar 2014 14:13:07 -0600 [thread overview]
Message-ID: <878usc8ros.fsf@gmail.com> (raw)
In-Reply-To: <877g7xazhr.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 14 Mar 2014 17:41:36 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Daniel Colascione <dancol@dancol.org> writes:
>
>> On 03/13/2014 05:36 PM, Eric M. Ludlam wrote:
>>> The key thing that EIEIO lets me do is define interfaces that allows
>>> modules to work together.
One more experiential point in this thread. I implemented an Emacs GO
mode recently and (thanks to EIEIO) I was able to transparently support
reading/writing of moves/game-state to/from multiple GO engines, network
protocols, game formats (sgf) and even the Emacs display and user, all
through a single API [1].
I would not have even attempted this without EIEIO, but with EIEIO it
was a pleasure.
Best,
Footnotes:
[1] https://raw.github.com/eschulte/el-go/master/go-api.el
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2014-03-14 20:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 3:04 About CEDET, Completion, and compilers Eric M. Ludlam
2014-03-13 13:40 ` Andreas Röhler
2014-03-13 14:04 ` João Távora
2014-03-13 14:21 ` Andreas Röhler
2014-03-14 0:36 ` Eric M. Ludlam
2014-03-14 2:26 ` EIEIO Daniel Colascione
2014-03-14 3:35 ` EIEIO Eric M. Ludlam
2014-03-14 6:42 ` EIEIO David Engster
2014-03-14 9:41 ` EIEIO Eric Abrahamsen
2014-03-14 20:13 ` Eric Schulte [this message]
2014-03-15 6:54 ` EIEIO Thien-Thi Nguyen
2014-03-16 1:06 ` ELPA Go integration Was: EIEIO Eric Schulte
2014-03-16 10:36 ` Thien-Thi Nguyen
2014-03-24 8:33 ` Thien-Thi Nguyen
2014-03-17 14:36 ` Stefan
2014-03-25 2:05 ` Stefan
2014-03-14 10:24 ` EIEIO João Távora
2014-03-14 6:47 ` About CEDET, Completion, and compilers Andreas Röhler
2014-03-23 14:57 ` Richard Stallman
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=878usc8ros.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.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.