Re: Macro for replacing a placeholder in an expression
Hello Linus! On 8/5/22 11:42, Linus Björnstam wrote: I wrote this, which does a tree fold over a sexp: https://hg.sr.ht/~bjoli/megacut/browse/readme.txt?rev=tip It is unhygienic currently, and I will probably never change because I only use it at the repl. The code is really just a syntax-case version of the fast and efficient flatten algorithm, but without flattening. I might study it later. Thank you for that. I have found a solution to my previous problems of expansion order using CK macros described at: https://okmij.org/ftp/Scheme/macros.html#ck-macros. Everything seems to work now, except some cases with vectors, I think only with vector syntax #(...). That is what I am still trying to figure out. However, the current code is in my repository of Guile examples. I would (perma-)link to it, but currently notabug has an issue. Using CK macros does make the macros simpler, although one must get the quoting right, which is sometimes confusing. Best regards, Zelphir -- repositories: https://notabug.org/ZelphirKaltstahl
Using Guile 2.2 modules with Guile 3
Hi, Say I want to use guile-dbi wich use Guile 2.2. Is there any danger for me to use it with Guile 3.0? I see that Guile will recompile the module because the already compiled one does not match, I guess. Other than that, any side effects? Regards, old -- Olivier Dion oldiob.dev
Re: Using Guile 2.2 modules with Guile 3
On 06-08-2022 17:11, Olivier Dion via General Guile related discussions wrote: Hi, Say I want to use guile-dbi wich use Guile 2.2. Is there any danger for me to use it with Guile 3.0? I see that Guile will recompile the module because the already compiled one does not match, I guess. Other than that, any side effects? Regards, old Going by the package definition, guile-dbd-postgresql seems to make a Guile extension (C). There have been incompatible changes (both on the Guile code level, and presumably on the C level). As such, sounds risky to me. Also, for whatever reason, guile-dbi propagates an old guile, so you'll get a propagation conflict without guarantees on which Guile version ‘wins’. Greetings, Maxime. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Using Guile 2.2 modules with Guile 3
On Sat, 06 Aug 2022, Maxime Devos wrote: > On 06-08-2022 17:11, Olivier Dion via General Guile related discussions > wrote: >> Hi, >> >> Say I want to use guile-dbi wich use Guile 2.2. Is there any danger for >> me to use it with Guile 3.0? I see that Guile will recompile the module >> because the already compiled one does not match, I guess. Other than >> that, any side effects? >> >> Regards, >> old >> > Going by the package definition, guile-dbd-postgresql seems to make a > Guile extension (C). There have been incompatible changes (both on the > Guile code level, and presumably on the C level). As such, sounds risky > to me. > > Also, for whatever reason, guile-dbi propagates an old guile, so you'll > get a propagation conflict without guarantees on which Guile version ‘wins’. > So I guess it would be better for me to use something like guile-sqlite3. -- Olivier Dion oldiob.dev
Re: Using Guile 2.2 modules with Guile 3
On 06-08-2022 17:31, Olivier Dion wrote: old Going by the package definition, guile-dbd-postgresql seems to make a Guile extension (C). There have been incompatible changes (both on the Guile code level, and presumably on the C level). As such, sounds risky to me. Also, for whatever reason, guile-dbi propagates an old guile, so you'll get a propagation conflict without guarantees on which Guile version ‘wins’. So I guess it would be better for me to use something like guile-sqlite3. Myself I think it would be better to update guile-dbi to the new Guile. There were a few incompatible changes between the two Guile major versions, but very little and easy to resolve in my experience. Greetings, Maxime. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
