unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Damien Mattei <damien.mattei@gmail.com>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: for with break and continue
Date: Mon, 5 Sep 2022 10:46:22 +0200	[thread overview]
Message-ID: <CADEOadeHvspy51B2cbgjhHjHNLzZhmiiUJxfXJnZbPAzZbKpOA@mail.gmail.com> (raw)
In-Reply-To: <5412ff25-5339-7399-4e48-23a8f5999956@abou-samra.fr>

very interesting.
Finally is our functions,at least one, for/bc compatible with R6RS? i can
not exactly figure it exactly, i see at leats identifier-syntax not in the
library index:
http://www.r6rs.org/final/html/r6rs-lib/r6rs-lib-Z-H-21.html#node_index_start
one day i will have to read the Dybvig article to understand all
that.Perhaps in a near future. ;-)
Damien


On Mon, Sep 5, 2022 at 2:42 AM Jean Abou Samra <jean@abou-samra.fr> wrote:

>
>
> Le 04/09/2022 à 16:41, Damien Mattei a écrit :
> > yes in fact a lot of function related to syntax (datum->syntax, etc)
> > are not in R6RS and R7RS-small,
>
>
> datum->syntax actually *is* R6RS, in the "libraries" document. See
> http://www.r6rs.org/final/r6rs-lib.pdf page 55.
>
> (It is not in R7RS small, since R7RS small doesn't even have syntax-case.)
>
>
> > i have to keep that in mind because i want to write a library that
> > could be portable between scheme implementation and that support
> > curly-infix ,less than a number of scheme that count with the fingers
> > of an hand ,at the end.... :-) but 'for was a disgression,i know
> > 'while of guile, again not standard...
> >
> > Regards,
> > Damien
> >
> > On Sun, Sep 4, 2022 at 2:40 PM Jean Abou Samra <jean@abou-samra.fr>
> wrote:
> >
> >
> >
> >     Le 04/09/2022 à 14:00, Damien Mattei a écrit :
> >     > yes very good
> >     > then break si not overwritten, using module, i do not know if
> >     modules
> >     > is finally standardised in R6RS, and in guile?
> >
> >
> >
> >     Guile supports R6RS libraries, but it's not the same as its
> >     traditional
> >     use-modules/define-module forms.
> >
> >
> https://www.gnu.org/software/guile/manual/html_node/R6RS-Libraries.html
> >
> >     But you're going to have a much more pressing problem with
> >     standardization: syntax parameters are not standard. So you're a bit
> >     stuck there.
> >
> >
> >
> >     > a few problem with module i hope to fix it later but it works with
> >     > your example, not sure let/ec is standart?
> >
> >
> >     let/ec is not standard, but exceptions are. See section 7 of the
> >     libraries document of R6RS:
> >
> >     http://www.r6rs.org/final/r6rs-lib.pdf
> >
> >     Best,
> >     Jean
> >
>
>


      reply	other threads:[~2022-09-05  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04  9:54 for with break and continue Damien Mattei
2022-09-04 10:43 ` Jean Abou Samra
2022-09-04 12:00   ` Damien Mattei
2022-09-04 12:40     ` Jean Abou Samra
2022-09-04 14:41       ` Damien Mattei
2022-09-05  0:42         ` Jean Abou Samra
2022-09-05  8:46           ` Damien Mattei [this message]

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=CADEOadeHvspy51B2cbgjhHjHNLzZhmiiUJxfXJnZbPAzZbKpOA@mail.gmail.com \
    --to=damien.mattei@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=jean@abou-samra.fr \
    /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).