From: Damien Mattei <damien.mattei@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: unrecognized syntax: type[args]
Date: Sat, 7 Oct 2023 18:34:22 +0200 [thread overview]
Message-ID: <CADEOadecK4C6OTZ1xdEbphKbtNUp_faCsdk3cuGAzX_Q2q+3ug@mail.gmail.com> (raw)
In-Reply-To: <CADEOaddWntmJ4zXK1eYrL13FouQbsLc5K6cMgUfxz0=HGFAGRA@mail.gmail.com>
i understand that in kawa there is an immediate evaluation of $bracket-apply$
but here i'm using $bracket-apply$ as a procedure (was a macro in the
past) that will be evaluated later at a point container-eval and
expr-eval are known.
And container-eval and expr-eval are not type in my code but variable
that could be vector,string,hash-table,arrays.... all that could be
indexing by one or more indexes.... [ ] as operator....
On Sat, Oct 7, 2023 at 6:30 PM Damien Mattei <damien.mattei@gmail.com> wrote:
>
> yes it it what i'm understanding:
>
> $bracket-apply$
> #<syntax <unnamed>>
>
> so Kawa already use $bracket-apply$ ,part of SRFI 105 but where is it
> documented i have to deal with that in relation with use i do within
> my code (i can of course rename $bracket-apply$ as i control the
> reader now...)
>
> lot of thing to understand before action....
>
> On Sat, Oct 7, 2023 at 5:35 PM Per Bothner <per@bothner.com> wrote:
> >
> >
> >
> > On 10/7/23 08:02, Damien Mattei via Kawa wrote:
> >
> > > #|.....19|# (for ((<+ k i2) (>= k i1) (<- k (+ k step)))
> > > #|.....20|# (<- ($bracket-apply$ container-eval k)
> > > ($bracket-apply$ expr-eval i))
> > > #|.....25|# (<- i (+ i 1)))))
> > > /dev/tty:20:44: unrecognized syntax: type[args]
> > > /dev/tty:24:44: unrecognized syntax: type[args]
> > >
> > >
> > > what does it means?
> >
> > It is referring to the ($bracket-apply$ container-eval k) and
> > ($bracket-apply$ expr-eval i) which are de-sugarings of
> > container-eval[k] and expr-eval[i].
> >
> > Specifically, container-eval and expr-eval are not valid known types.
> > --
> > --Per Bothner
> > per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2023-10-07 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 15:02 Damien Mattei
2023-10-07 15:34 ` Per Bothner
2023-10-07 16:30 ` Damien Mattei
2023-10-07 16:34 ` Damien Mattei [this message]
2023-10-07 16:42 ` Per Bothner
2023-10-07 16:59 ` Damien Mattei
2023-10-08 8:11 ` Damien Mattei
2023-10-08 9:02 ` Damien Mattei
2023-10-08 9:15 ` Damien Mattei
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADEOadecK4C6OTZ1xdEbphKbtNUp_faCsdk3cuGAzX_Q2q+3ug@mail.gmail.com \
--to=damien.mattei@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.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).