unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Guile and Mes [WAS: conflicts in the gnu project now affect guile]
Date: Sat, 19 Oct 2019 09:51:41 +0200	[thread overview]
Message-ID: <87eez9mauq.fsf_-_@gnu.org> (raw)
In-Reply-To: <87lfti1pp0.fsf@netris.org> (Mark H. Weaver's message of "Fri, 18 Oct 2019 03:24:00 -0400")

Mark H Weaver writes:

Hi Mark,

>> I have been worrying a bit about this change because I do not see how to
>> implement it in Mes.
>
> There's a straightforward way to translate a body containing mixed
> definitions and expressions into a 'letrec*'.  It's illustrated in the
> commit log, and in the manual:
>
>   https://git.savannah.gnu.org/cgit/guile.git/commit/?id=20535922147cd5992330962aaa5c4986563fc905
>   https://git.savannah.gnu.org/cgit/guile.git/tree/doc/ref/api-binding.texi?id=5284b9b9c6cecc404a912acaefce2b883ac0dbba#n284

Thanks!  I really appreciate your help.  Andy found me on IRC and also
helped me with two similar suggestions.  It's great that you both have
helped take away my worries here.

Even better, these solutions got me thinking about how Mes implements
macros and Guile compatibility.  Our next big target for Mes should be
to remove define-macro support from eval_apply and load Guile's
psyntax-pp.scm.  Probably best to start playing with Guile stable-2.0
and first reduce psyntax.scm to the bare minimum, regenerate
psyntax-pp.scm and get a easier success and work from that.

Greetings,
janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com



  reply	other threads:[~2019-10-19  7:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 13:14 conflicts in the gnu project now affect guile Andy Wingo
2019-10-16 14:11 ` Thompson, David
2019-10-16 15:33   ` Christopher Lemmer Webber
2019-10-16 16:10     ` Eli Zaretskii
2019-10-19 17:05       ` Mark H Weaver
2019-10-16 18:27     ` Jean Louis
2019-10-16 18:27   ` Jean Louis
2019-10-16 19:30   ` pelzflorian (Florian Pelz)
2019-10-18  9:44     ` Alex Sassmannshausen
2019-10-16 18:12 ` Jean Louis
     [not found]   ` <CAGua6m3d_t2hd7P2ueTsPZytF7pNO7f8xptBWofPw9UvyYWDaw@mail.gmail.com>
2019-10-16 21:32     ` Fwd: " Stefan Israelsson Tampe
2019-10-16 21:56   ` Tadeus Prastowo
2019-10-16 22:05     ` Adrienne G. Thompson
2019-10-18  3:16       ` Richard Stallman
2019-10-18  3:17     ` Richard Stallman
2019-10-18 10:37       ` Tadeus Prastowo
2019-10-16 19:21 ` Mikael Djurfeldt
2019-10-16 21:03 ` Linus Björnstam
2019-10-17  0:18 ` Arne Babenhauserheide
2019-10-17  1:24 ` Mark H Weaver
2019-10-17  7:07   ` Jan Nieuwenhuizen
2019-10-18  7:24     ` Mark H Weaver
2019-10-19  7:51       ` Jan Nieuwenhuizen [this message]
2019-10-19  8:56         ` Guile and Mes [WAS: conflicts in the gnu project now affect guile] Mikael Djurfeldt
2019-10-18 11:20     ` conflicts in the gnu project now affect guile Christopher Lemmer Webber
2019-10-18 13:14       ` Mark H Weaver
2019-10-18 13:33         ` Christopher Lemmer Webber
2019-10-18 13:49           ` Thompson, David
2019-10-17  1:40 ` Mike Gran
2019-10-17  2:11 ` Neil Van Dyke
2019-10-17 18:11 ` Mikhail Kryshen
2019-10-18  9:26   ` Alex Sassmannshausen
2019-10-19  4:03     ` Mikhail Kryshen
2019-10-18  1:06 ` Mark H Weaver
2019-10-18  6:31   ` Nala Ginrut
2019-10-18  9:20   ` Mikael Djurfeldt
2019-10-18 14:22   ` Ludovic Courtès
2019-10-19 22:55 ` Taylan Kammer
2019-10-20  3:08   ` Mark H Weaver
2019-10-20  3:54     ` Nala Ginrut
2019-10-20 19:12     ` Taylan Kammer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eez9mauq.fsf_-_@gnu.org \
    --to=janneke@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.org \
    --cc=wingo@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).