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.help Subject: Re: Lookarounds and recursion in Emacs regexes Date: Mon, 06 Feb 2023 15:23:09 +0200 Message-ID: <838rhbq66a.fsf@gnu.org> References: <87h6wbeti3.fsf@mbork.pl> <877cx7n5an.fsf@dataswamp.org> <831qn4u0b4.fsf@gnu.org> <87bkm76jkr.fsf@dataswamp.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38983"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 06 14:24:24 2023 Return-path: Envelope-to: geh-help-gnu-emacs@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 1pP1Tr-0009xs-Si for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 06 Feb 2023 14:24:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pP1T6-0001Uv-81; Mon, 06 Feb 2023 08:23:36 -0500 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 1pP1SY-0001OO-08 for help-gnu-emacs@gnu.org; Mon, 06 Feb 2023 08:23:11 -0500 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 1pP1SV-000291-Gk for help-gnu-emacs@gnu.org; Mon, 06 Feb 2023 08:23:01 -0500 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=Y+tmBI4d8cJMAqXDhmy1spzvdSm3pPi+hD7Vcs3V7ew=; b=dGUQRfKckeJk a5ynk3vfys060NMKtke7Duj+k/F2jNmjDlTaTSYKn5vLquiDUjR7Ai3UhcOI/7XZbeyAP9IYrEDvr 624PPVxmvnB+P3EVHBSZQvwk/sQySrED4cQg9+XNoaK4NYpAA0UvdVQ/BbIPxsIpF6uh43WoI8+y6 +RRejUYIqIRxtMUQTqYECsSQerrYXpKb7ghIphj4Ov9hhRgmD3jX4OgzPU36rApbdvTLfMne25c3S LkqrlT25MFFG/4s5/mWhG3Xvfl05A5VGtqbxRqw3WLriWB4dzjbIKfvzvFxilTQWu/gRe8nH+JN6J QkNtKtt4dm5IGBZXB/n53w==; 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 1pP1SS-00062c-NP for help-gnu-emacs@gnu.org; Mon, 06 Feb 2023 08:22:58 -0500 In-Reply-To: <87bkm76jkr.fsf@dataswamp.org> (message from Emanuel Berg on Mon, 06 Feb 2023 13:53:56 +0100) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:142621 Archived-At: > From: Emanuel Berg > Date: Mon, 06 Feb 2023 13:53:56 +0100 > > Eli Zaretskii wrote: > > >> It doesn't prevent adding other extension languages, nor > >> even does it necessarily prevent changing the > >> implementation language to another one in theory. > > > > Indeed, but replacing ELisp would probably need to rewrite > > a lot of internals currently implemented in C, since most, > > if not all, of them are currently very tightly coupled with > > Lisp and assume the existence and design/implementation of > > various aspects of the Lisp machine. > > I don't think anyone suggests replacing Elisp Stefan did, in the part cited above. he didn't suggest it, but he said it's not prevented. And I replied to that part.