From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Concurrency via isolated process/thread Date: Mon, 24 Jul 2023 16:41:28 +0300 Message-ID: <837cqps9yv.fsf@gnu.org> References: <871qhnr4ty.fsf@localhost> <83ilawhpi6.fsf@gnu.org> <87zg48apwr.fsf@localhost> <83edljg8ub.fsf@gnu.org> <87o7knbxr7.fsf@localhost> <838rbrg4mg.fsf@gnu.org> <87ilavbvdr.fsf@localhost> <834jmffvhy.fsf@gnu.org> <878rbrbmwr.fsf@localhost> <83fs5zecpo.fsf@gnu.org> <87351zbi72.fsf@localhost> <83351yevde.fsf@gnu.org> <87cz12ad2w.fsf@localhost> <83a5w6cwdr.fsf@gnu.org> <87pm518m0g.fsf@localhost> <83o7kl9tyj.fsf@gnu.org> <874jmd89us.fsf@localhost> <878rb53dkj.fsf@localhost> <87wmyp1vr9.fsf@yahoo.com> <875y6939jl.fsf@localhost> <83cz0hscbp.fsf@gnu.org> <87r0ox1md0.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38484"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jul 24 15:41:49 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qNvor-0009pO-H1 for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Jul 2023 15:41:49 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qNvo9-0000TZ-RJ; Mon, 24 Jul 2023 09:41:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qNvo7-0000T2-Qn for emacs-devel@gnu.org; Mon, 24 Jul 2023 09:41:03 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qNvo4-0002Eu-FC; Mon, 24 Jul 2023 09:41:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Z/ALIqugXN4SDCemEDosjQ3PKxksHj/4jks7dM8ANEo=; b=Vn0/2RcsIltl tahJRO+72AAEMiO6x1ZqamXIrnCrtOYqO8wIAjvkzYEl0KZTZfhYrPYGF/lz99+jbxoXcduXbtmu2 x67o1WJUZNNmVrxIO+GHa6u5NEwRbGEW3q0cRu8xLZQ1clKSXGIl0JC4rS3+e44qIxnWAaauU8Tri VgKvtCOGVSqJM3JMVg5YVFBeFtRwpXc99jgQEU+bYhnXyumAITYNr3VRzDMGdJCuL1zhW2kMTORQr s05oPHk70+5RbmFTEDpeBoNpY5L51mKKA3Zbpri1KDhTP6VcTGmJU4+/lj4g60Zh8eWORWnLWB/em KQiSeosdDVqFOqtslQbLgg==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qNvnt-0006nQ-Om; Mon, 24 Jul 2023 09:41:00 -0400 In-Reply-To: <87r0ox1md0.fsf@localhost> (message from Ihor Radchenko on Mon, 24 Jul 2023 13:15:55 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:308058 Archived-At: > From: Ihor Radchenko > Cc: luangruo@yahoo.com, emacs-devel@gnu.org > Date: Mon, 24 Jul 2023 13:15:55 +0000 > > Eli Zaretskii writes: > > > #define PT (current_buffer->pt + 0) > > > > automagically makes PT refer to the current buffer, so the code only > > needs to change current_buffer to have PT set correctly. > > > > By contrast, you propose to have one value of point per thread, which > > means a thread that switches buffers will have to manually change all > > of these values, one by one. Why is that a good idea? > > Switching buffer already involves juggling with pt_marker_ in > record_buffer_markers and fetch_buffer_markers. No, it doesn't, not if the code only sets current_buffer. > > And what about C code which copies/moves text between two buffers? > > For example, some primitives in coding.c can decode text from one > > buffer while writing the decoded text into another. > > They still use set_buffer_internal. That's not necessary for some operations.