From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: syntax question for defun
Date: Thu, 29 Aug 2024 15:28:12 -0400 [thread overview]
Message-ID: <jwv34mnuo7b.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 7c5c55a8-59bc-4d2e-9fee-bd924a323470@greatalpha.com
> Some elisp code from 2018, not (yet) intended for anyone (else). I'm sure
> there are many ways, per knowledgeable folks such as yourself, to improve
> the approach/style, and I'm all ears. This is just a snippet of what I was
> starting with:
You might enjoy
Eoops: an object-oriented programming system for Emacs-Lisp
Houser, Chris and Kalter, Scott D. (1992)
https://dl.acm.org/doi/10.1145/147135.147248
https://www.emacswiki.org/emacs/EmacsObjectOrientedProgrammingSystem
- Stefan
prev parent reply other threads:[~2024-08-29 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 20:01 syntax question for defun David Elson
2024-08-29 4:57 ` tomas
2024-08-29 16:45 ` David Elson
2024-08-29 18:29 ` tomas
2024-08-29 19:28 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
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=jwv34mnuo7b.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).