all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomas Hlavaty <tom@logand.com>
To: LdBeth <andpuke@foxmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: using finalizers
Date: Fri, 31 Dec 2021 13:01:11 +0100	[thread overview]
Message-ID: <875yr5m1a0.fsf@logand.com> (raw)
In-Reply-To: <tencent_2D2DBEDBD2B1AB4702C35567C6CAEBAFD105@qq.com>

On Fri 31 Dec 2021 at 19:41, LdBeth <andpuke@foxmail.com> wrote:
>>>>>> In <87bl0xm39e.fsf@logand.com> 
>>>>>>	Tomas Hlavaty <tom@logand.com> wrote:
>
> ldb> You would only need finalizers for complex objects, so ideally you
> ldb> could use OOP to manage that, probably EIEIO but not limited to that,
> ldb> and you may even come up with your own.
>
> Tomas> What do you mean?
>
> Tomas> Why not do it "properly" and future-proof the make-finalizer interface,
> Tomas> pass the object explicitly there and leave the rest as implementation
> Tomas> detail instead of leaking the issue to the programmer?
>
> Isn't it doesn't make sense to associate a primitive data types such
> as numbers, symbols, strings with a finalizer? If you need such a
> feature on primitive data types, you are probably using this in a way
> not intended.
>
> And meawhile it would be problematic to hardcode what kinds of objects
> are allowed to have objects. Notice this is a C function so it is not
> very flexible.

This is irrelevant, I am not talking about that.

> You can think this is the primitive API that Emacs provides, and
> people can build up more higher level ones that suit their particular
> needs.

This primitive API that Emacs provides relies on the implicit assumption
of the compiler being not smart.  I do not see how that is a good idea.



  reply	other threads:[~2021-12-31 12:01 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 22:43 using finalizers Tomas Hlavaty
2021-12-31  2:46 ` LdBeth
2021-12-31  3:29   ` Stefan Monnier
2021-12-31  3:36     ` Stefan Monnier
2021-12-31  4:30     ` LdBeth
2021-12-31  4:43       ` LdBeth
2021-12-31  6:28   ` Tomas Hlavaty
2021-12-31 10:59     ` LdBeth
2021-12-31 11:18       ` Tomas Hlavaty
2021-12-31 11:41         ` LdBeth
2021-12-31 12:01           ` Tomas Hlavaty [this message]
2022-01-01 17:00     ` Stefan Monnier
2022-01-01 20:25       ` Tomas Hlavaty
2022-01-01 20:47         ` Stefan Monnier
2022-01-01 22:55           ` Tomas Hlavaty
2022-01-01 23:18             ` Stefan Monnier
2022-01-01 23:47               ` Tomas Hlavaty
2022-01-01 23:26             ` Tomas Hlavaty
2021-12-31  7:50   ` Eli Zaretskii
2021-12-31  9:31     ` Tomas Hlavaty
2021-12-31 12:27       ` Eli Zaretskii
2022-01-01 17:58         ` Tomas Hlavaty
2022-01-01 18:20           ` Eli Zaretskii
2022-01-01 20:55             ` Stefan Monnier
2022-01-01 23:05               ` Tomas Hlavaty
2022-01-01 23:21                 ` Stefan Monnier
2021-12-31 14:23       ` Rudolf Schlatte
2021-12-31 16:21         ` Stefan Monnier
2022-01-01 17:37           ` Tomas Hlavaty
2022-01-01 22:36         ` Tomas Hlavaty
2022-01-02  6:54           ` Eli Zaretskii
2022-01-02  7:53             ` Tomas Hlavaty
2022-01-02  8:33               ` Eli Zaretskii
2022-01-02 13:10                 ` Tomas Hlavaty
2022-01-02 14:42                   ` Eli Zaretskii
2022-01-02 15:16                     ` Eli Zaretskii
2022-01-02 17:18                       ` Tomas Hlavaty
2022-01-02 18:11           ` Rudolf Schlatte
2022-01-03  0:37             ` Tomas Hlavaty
2022-01-04  3:08               ` Richard Stallman
2021-12-31 14:39 ` LdBeth
2022-01-01 17:59   ` Tomas Hlavaty

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=875yr5m1a0.fsf@logand.com \
    --to=tom@logand.com \
    --cc=andpuke@foxmail.com \
    --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 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.