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: prior work on non-backtracking regex engine? Date: Wed, 13 Mar 2024 13:23:42 +0000 Message-ID: <87il1qw9i9.fsf@localhost> References: <3a9IKoS2YLqJYosdfpFVdq8ashG0LPPJdB-ugdUgJEqM6-O3RWFeCu01FUPYBsp87xchkX-z1PRlNqJQm8ge_h3v0ziCWcME2fx-6PW-UP4=@hypnicjerk.ai> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22105"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "emacs-devel@gnu.org" To: Danny McClanahan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Mar 13 14:20:30 2024 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 1rkOWz-0005ZL-Nb for ged-emacs-devel@m.gmane-mx.org; Wed, 13 Mar 2024 14:20:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rkOWG-0002Z9-E6; Wed, 13 Mar 2024 09:19:45 -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 1rkOW8-0002X2-OS for emacs-devel@gnu.org; Wed, 13 Mar 2024 09:19:36 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rkOW6-0001yX-5t for emacs-devel@gnu.org; Wed, 13 Mar 2024 09:19:36 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 8130A240027 for ; Wed, 13 Mar 2024 14:19:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1710335971; bh=GB9wzo6pDD1H7kJBhBH3gPQOqpUl8sdleUssF+kxsCE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=IFISHPBDGn++pPjOHV2lyWKLdghdlf9q+unv8T3VYtTtbkvpH7LKIE56yFFN/n0FW bMS3CCAPT4Qx7KiR5qtBQuo5Ip1DqY8vnI4Yr9jfbSBj65UkBdX9rOjAK0P6BAC2Yg SXjkrSQVfKT3JYHOWjzAmDecyPvB9fknrMEkyIZyL1C93t+045PiMhrLi6zcQezUUO vtBhGQDuT7WEiaXbM38SF3cQwMBZI2+NObKHSmYVvNmQBcbaYi015ZNs5E/46OjjSj dkjeAqCOngxftiUQ4uNcwSqFo33mnEOtXG2OhH8x+eZ9YD2V9vlgSwJyDZYOSvZ5EF cdO8vzHZm7Fbg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TvrhL5VRSz6tmv; Wed, 13 Mar 2024 14:19:30 +0100 (CET) In-Reply-To: Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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_H3=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=ham 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:317034 Archived-At: Danny McClanahan writes: > (4) What is the best way to package third-party code for emacs? > > I was thinking of architecting this regex engine as a third-party > codebase exposing a C ABI shared library, which the emacs build system > could detect as an optional dependency (like libjansson). I was hoping > to use rust to implement this regex engine, but I know that a cargo > package alone isn't enough for non-rust code to depend on: I was also > planning to maintain package recipes for this regex engine for > multiple linux distros, so that emacs could easily add it to the build > system (like librsvg). Are there any further constraints I should know > about for optional dependencies in the emacs build system? AFAIR, previous discussions raised some concerns about using Rust in particular: https://yhetil.org/emacs-devel/E1pKAM0-0001Ss-W6@fencepost.gnu.org/ Because of Rust volatility and some license issues. That said, the linked discussion was not about linking to rust libraries via C ABI, but about contributing Rust code to Emacs core directly. Another somewhat relevant discussion is https://yhetil.org/emacs-devel/95980ffc-86e7-ad54-4a20-539d8c6ea5d0@mailo.com/ P.S. Better regexp engine would be very welcome. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at