unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Damien Mattei <damien.mattei@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: macro syntax-error works in prefix but not curly-infix
Date: Mon, 20 Sep 2021 11:16:05 +0200	[thread overview]
Message-ID: <CADEOadfAQE6Vg5emEfU6FNAnK9BFhi1QgF2rqE49OYfqoyaUPA@mail.gmail.com> (raw)
In-Reply-To: <44267709-9cc3-5185-86b7-02adc7a17d1e@posteo.de>

hello Zelphir,

i understood my error, all was ok is just that  it convert this way:
'{x <+ 2 3}
($nfx$ x <+ 2 3)

in general the prefix notation of  {1 <+ 2 3 4 ...} is not (<+ 1 2 3 4 ...)
because (<+ 1 2 3 4 ...) in infix is {1 <+ 2 <+ 3 <+ 4 <+ ...}

it a stupid error of mine

i will drop the error case in macro and let Scheme deal with the error
itself ,he do it fine...
we message like that:

Syntax error:
unknown location: source expression failed to match any pattern in form <+

i find the error because thinking to ellipsis make me thiink to multiple
expressions in my <+ operator,anyway you help me, thank you

<+ is just in this case a define:

scheme@(guile-user)> {x <+ 7}
scheme@(guile-user)> x
7
he must be an unary operator , it does not allow multiple arity, but that
could be an idea like in C or as far as i remember one can writ x=y=7,
anyway in scheme it would be harder because SRFI 105 does not deal with
precedence... well i will do that in the future  and such writing as x=y=7
is not often used....
thank you


damien


On Sun, Sep 19, 2021 at 2:34 PM Zelphir Kaltstahl <
zelphirkaltstahl@posteo.de> wrote:

> Hi Damien!
>
> I think there might be too few expressions matched in the first case: (_
> var expr). Wouldn't it have to be:
>
> ~~~~
> (_ var expr1 expr2)
> ;; or
> (_ var exprs ...)
> ~~~~
>
> for
>
> ~~~~
> (<+ var expr1 expr2)
> ~~~~
>
> to work, simply because of the number of expressions there?
>
> But then you might need to use ellipsis in the resulting syntax somewhere,
> otherwise you get:
>
> ~~~~
> syntax: missing ellipsis in form (syntax (define var expr))
> ~~~~
>
> I don't know where that would go, but I also do not understand yet the
> goal. I think it is best to always describe, what you want to achieve, when
> you write a macro.
>
> Regards,
> Zelphir
> On 9/4/21 4:41 PM, Damien Mattei wrote:
>
> hi,
>
> i have this macro:
>
> (define-syntax <+
>   (syntax-rules ()
>     ((_ var expr) (define var expr))
>     ((_ err ...) (syntax-error "Bad <- form")) ;; does not work in infix !
>     ))
>
> why my syntax-error pattern never reach in infix:
>
> scheme@(guile-user)> {x <+ 7 8}
> While compiling expression:
> Syntax error:
> unknown file:3:3: source expression failed to match any pattern in form <+
>
> but ok in prefix:
>
> scheme@(guile-user)> (<+ x 9 10)
> While compiling expression:
> Syntax error:
> unknown location: <+: Bad <- form in form (<+ x 9 10)
>
> why?
> Regards,
> Damien
>
> --
> repositories: https://notabug.org/ZelphirKaltstahl
>
>


      reply	other threads:[~2021-09-20  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 14:41 macro syntax-error works in prefix but not curly-infix Damien Mattei
2021-09-19  6:23 ` adriano
2021-09-19  7:48   ` Damien Mattei
2021-09-19 12:34 ` Zelphir Kaltstahl
2021-09-20  9:16   ` 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=CADEOadfAQE6Vg5emEfU6FNAnK9BFhi1QgF2rqE49OYfqoyaUPA@mail.gmail.com \
    --to=damien.mattei@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=zelphirkaltstahl@posteo.de \
    /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).