From: Adam Porter <adam@alphapapa.net>
To: rms@gnu.org, Lynn Winebarger <owinebar@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [GNU ELPA] New package: tam
Date: Fri, 22 Sep 2023 14:45:49 -0500 [thread overview]
Message-ID: <2dc05d96-a8f4-ee0b-3ec4-d0403f89744a@alphapapa.net> (raw)
In-Reply-To: <E1qjQG1-0003rk-Bg@fencepost.gnu.org>
On 9/21/23 15:26, Richard Stallman wrote:
> > Thanks for taking a look. The reason is that I was thinking about
> > adding functionality for pools of preallocated objects that leverage
> > the tables for tracking which objects are actually being used.
>
> I don't have much of a picture of what you're using this for.
> For all I know, maybe it is a good method for that use.
>
> But it does seem un-lispy.
Agreed. I am interested in it, but I'd like to know more about what
problem it's intended to solve. e.g. I've had functions that certainly
do allocation and GC in a process sentinel, and AFAIK that hasn't been a
problem. But a project I'm working on may exercise this kind of
functionality more in the future, so maybe tam.el could be helpful.
next prev parent reply other threads:[~2023-09-22 19:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 2:28 [GNU ELPA] New package: tam Lynn Winebarger
2023-09-18 9:37 ` Philip Kaludercic
2023-09-18 16:22 ` Lynn Winebarger
2023-09-18 17:02 ` Philip Kaludercic
2023-09-19 15:38 ` Lynn Winebarger
2023-09-20 8:26 ` Philip Kaludercic
2023-09-20 16:14 ` Lynn Winebarger
2023-09-20 17:30 ` Stefan Monnier via Emacs development discussions.
2023-09-21 4:21 ` Lynn Winebarger
2023-09-21 13:59 ` Stefan Monnier
2023-09-22 3:01 ` Lynn Winebarger
2023-09-22 3:23 ` Stefan Monnier
2023-09-21 16:38 ` Philip Kaludercic
2023-09-18 19:26 ` Adam Porter
2023-09-19 15:48 ` Lynn Winebarger
2023-09-19 16:29 ` Adam Porter
2023-09-21 20:26 ` Richard Stallman
2023-09-22 19:45 ` Adam Porter [this message]
2023-09-20 16:06 ` Stefan Monnier
2023-09-20 16:44 ` Lynn Winebarger
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=2dc05d96-a8f4-ee0b-3ec4-d0403f89744a@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=owinebar@gmail.com \
--cc=rms@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).