public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
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: Sun, 8 Oct 2023 10:11:48 +0200	[thread overview]
Message-ID: <CADEOadcy3mYVJdw=oTqGaryhaDHOMJ63-n4ORcAohoJm9zqOOg@mail.gmail.com> (raw)
In-Reply-To: <CADEOade3jm=XYO_8G2z_W5S9=m+eiA4_jdrURprvfcvt=mUK8A@mail.gmail.com>

it is hard to modify without touching or breaking deeply the kawa code
or my code because $bracket-apply$ is coded in java in
BracketApply.java
do you know a way to rename $bracket-apply$ it. The standart scheme
way i know does not work, the cause seems to be that it is java behind
, it is not a macro ,not a procedure:
#|kawa:9|# $bracket-apply$
#<syntax <unnamed>>
i ideally want to rewrite $bracket-apply$ and be able to reuse in it
the code of the previous definition of $bracket-apply$....

first problem is to rename this "object" $bracket-apply$ in kawa ?

On Sat, Oct 7, 2023 at 6:59 PM Damien Mattei <damien.mattei@gmail.com> wrote:
>
> yes it is what i was understanding and verifying:
>
> https://www.gnu.org/software/kawa/tutorial/Types.html
>
>
> |kawa:21|# (define x (int[] 1 2 3))
> #|kawa:22|# x
> [1 2 3]
>
> i discover that:
> #|kawa:23|# (define x (($bracket-apply$ int) 1 2 3))
> #|kawa:24|# x
> [1 2 3]
>
> yes i can redefining , that was in my code , but it fails, probably
> one of my definition used it before redefinition , i will test that
> and in the worse case use another keyword than  $bracket-apply$ when
> curly-infix2prefix.scm parse the [ ] and convert it in prefix....
>
> On Sat, Oct 7, 2023 at 6:42 PM Per Bothner <per@bothner.com> wrote:
> >
> > In Kawa $bracked-apply$ is a pre-defined macro - but it is not hard-wired.
> > You can re-bind it to something else.  You probably should.
> > Either that, or change the reader to conervt foo[args] to something different.
> > --
> >         --Per Bothner
> > per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2023-10-08  8:12 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
2023-10-07 16:42       ` Per Bothner
2023-10-07 16:59         ` Damien Mattei
2023-10-08  8:11           ` Damien Mattei [this message]
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='CADEOadcy3mYVJdw=oTqGaryhaDHOMJ63-n4ORcAohoJm9zqOOg@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).