From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Concurrency via isolated process/thread Date: Thu, 06 Jul 2023 15:09:06 +0000 Message-ID: <87ttuhxejx.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <83v8ezk3cj.fsf@gnu.org> <87v8ezpov0.fsf@localhost> <83r0pnk2az.fsf@gnu.org> <87pm57pns8.fsf@localhost> <87lefvp55t.fsf@yahoo.com> <87sfa28ura.fsf@localhost> <87cz16o8vz.fsf@yahoo.com> <87jzve8r4m.fsf@localhost> <871qhmo5nv.fsf@yahoo.com> <87bkgq8p5t.fsf@localhost> <87leftnat6.fsf@yahoo.com> <87fs6171uj.fsf@localhost> <83zg49gmgl.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35543"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jul 06 17:10:06 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 1qHQcP-00090I-Nb for ged-emacs-devel@m.gmane-mx.org; Thu, 06 Jul 2023 17:10:05 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qHQbb-0005fj-OJ; Thu, 06 Jul 2023 11:09:16 -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 1qHQbZ-0005fS-R4 for emacs-devel@gnu.org; Thu, 06 Jul 2023 11:09:14 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qHQbU-0001XY-Ru for emacs-devel@gnu.org; Thu, 06 Jul 2023 11:09:12 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 04B4B240101 for ; Thu, 6 Jul 2023 17:09:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688656147; bh=NF8VmymRMhrMWAjzIzb2e20QXLGJc91AurXSsv9c6t0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=Zk2gLGptAYtYu4VlJ+5KzO2yU4c+hf5tLW/Z7x2IFX1nqMpW50S2HNuLXvX8M9RxQ 3K5WbtJm3oOQWhaVh2gFp8jvAJ4mATykZLXn+MGW9E1MDaaiCHHudy/vqeugYPsj0g 1akMxJ+kmFFEdhXgiiwWrr9j7OUnW9YqlND3TmQdg5oNWg2FJU1lkjf5x0puDi8PWp UG6t9a6XA0UO6s2atWZvdULYaN9EOBg5r/H0nY4rlsSRiGjizajYHaBn8YDrUr9OUT R08Af2d1h54b94mOHzzCiIcx911gQID28b9pn4zPnkAS/1R8SKXNO5khzLljtszPY1 hIfchhAklZp1g== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Qxg0d1pXmz6tvJ; Thu, 6 Jul 2023 17:09:05 +0200 (CEST) In-Reply-To: <83zg49gmgl.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action 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:307512 Archived-At: Eli Zaretskii writes: >> Do you mean that binary communication is already possible? If so, is it >> documented somewhere? > > What is the difference between binary and text in this context, in > your interpretation? AFAIK, process communication is now implemented using buffers that, even in the absence of coding system, index the data stream into byte array. I am not sure if it is something that can be directly fed to memcpy (thus avoiding too much of extra cost for passing Lisp data around). > (I'm surprised to hear they are perceived as > different by someone who comes from Posix background, not MS-Windows > background.) I was looking at this from C perspective. And I am used to see Posix as text-based. At most, structured text like https://www.nushell.sh/ Maybe I am too young. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at