From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Newsgroups: gmane.lisp.guile.user Subject: Re: rfc: next guile 1.8.x release Date: Mon, 01 Feb 2021 22:49:10 +0100 Message-ID: <87k0rrh31l.fsf@gnu.org> References: <87ft38jw4h.fsf@gnuvola.org> <874kizh1er.fsf@gnu.org> <878s8b71d6.fsf@web.de> <871re2ip29.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26296"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cc: guile-user@gnu.org To: Massimiliano Gubinelli Original-X-From: guile-user-bounces+guile-user=m.gmane-mx.org@gnu.org Mon Feb 01 22:51:24 2021 Return-path: Envelope-to: guile-user@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 1l6h6S-0006eL-GD for guile-user@m.gmane-mx.org; Mon, 01 Feb 2021 22:51:24 +0100 Original-Received: from localhost ([::1]:50194 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l6h6R-0002Hf-FP for guile-user@m.gmane-mx.org; Mon, 01 Feb 2021 16:51:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46504) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l6h4L-0001oe-MV for guile-user@gnu.org; Mon, 01 Feb 2021 16:49:14 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34135) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l6h4K-0005jl-UQ; Mon, 01 Feb 2021 16:49:13 -0500 Original-Received: from [2a01:e0a:1d:7270:af76:b9b:ca24:c465] (port=52064 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1l6h4K-0002Xg-2K; Mon, 01 Feb 2021 16:49:12 -0500 X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 13 =?utf-8?Q?Pluvi=C3=B4se?= an 229 de la =?utf-8?Q?R=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu In-Reply-To: (Massimiliano Gubinelli's message of "Sun, 31 Jan 2021 18:35:58 +0100") X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane-mx.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.io gmane.lisp.guile.user:17221 Archived-At: Hi Massimiliano, Thanks for the needs of TeXmacs this clearly. A few comments below=E2=80=A6 Massimiliano Gubinelli skribis: > all these three features point to weakness of various possible solutions > > 1) we do not need a Scheme with a lot of OS interfaces, this duplicate fu= nctionalities in QT and in our own code. For example all the OS interaction= is dealt with internal functions (also because TeXmacs has its own virtual= filesystem). We do not need threads, GMP, etc... all these additional part= s add bloat without providing real useful functionalities. Threads and bignums (GMP) were already in 1.8 though, and overall libguile exposes about as much functionality today than in 1.8. But I can see that Qt and Guile are =E2=80=9Ccompeting=E2=80=9D feature-wise. > 2) it is better for us to have a Scheme which is not picky wrt. encodings= .=20 You can use binary output for when you just want to write bytes (info "(guile) Binary I/O"). > 3) compiled schemes or schemes without first-class modules are more diffi= cult to adapt to our own flavour of scheme coding. I don=E2=80=99t think this is necessarily the case. Probably you=E2=80=99l= l want a .scm -> .go rule in your makefiles, but that=E2=80=99s about it. > Currently I'm trying three different routes: > > - embed S7 (which is fast, dynamic and minimal and works everywhere) > - go for Guile 3 (I've still problems with phasing of macro expansion and= bootstrap of our codebase. Will it work on Windows? Do we really need to c= arry on all the code we do not use?) > - go for Chez Scheme (like for Guile 3 problems with compilation phases a= nd bootstrap of our codebase. I'm more confident it will work on Windows an= d on new architecture, it is more compact than Guile, essentially only the = compiler, I've still problems with the garbage collector at the level of C+= + interface). It=E2=80=99s much easier to port from Guile to Guile than from Guile to something else. :-) The extra =E2=80=9Ccode you don=E2=80=99t use=E2=80=9D in Guile can be seen= as a weight, but longer-term, it could also change the way you approach problems in TeXmacs and the way you structure it. Guile 3 can be embedded just like Guile 1, but it supports a much broader range of applications by being faster and providing more tools. Ludo=E2=80=99.