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: phiroc@free.fr, kawa@sourceware.org,
	 Jean-Paul Roy <jean-paul.roy@unice.fr>
Subject: Re: define-syntax can only be used with local variables
Date: Tue, 14 Sep 2021 20:00:02 +0200	[thread overview]
Message-ID: <CADEOadcuxmR3Zp_thzjPY+A2rGTh+yFjJ62H-80f=8760F_iKg@mail.gmail.com> (raw)
In-Reply-To: <CADEOadf6cMSqW6j9hLBkhT+UK_m9k+45toJeipWnAGOPQr8WYg@mail.gmail.com>

i know nothing ,sorry for the typos

On Tue, Sep 14, 2021 at 7:58 PM Damien Mattei <damien.mattei@gmail.com>
wrote:

> hello Per,
> it is strange when downloading source and trying to compile it with same
> openjdk 16 than the one use by binary i got two errors, the first one being:
> javac -d . -classpath ".:.:$CLASSPATH" -g @tmp-sources1.list
> ./gnu/lists/CharSeq.java:11: error: types CharSequence and Sequence<E> are
> incompatible;
> it could be helpful to understand why before thinking to a problem of
> hygiene because all is running well in kawa-2.1, i admit it is old and i do
> nothing about what happen between those long times....
> Damien
>
> On Tue, Sep 14, 2021 at 7:27 PM Per Bothner <per@bothner.com> wrote:
>
>>
>>
>> On 9/10/21 12:33 AM, phiroc--- via Kawa wrote:
>> > Hello,
>> > in the below code, nil! and nil2! only set variables values to '() and
>> '(0) when such variables are local (let).
>>
>> I'm guessing (without having tested it) that the restriction isn't local
>> variables
>> but lexical vs dynamic variables.  I.e. it is likely that module-level
>> (library-level)
>> variables would also work.
>>
>> Probably a problem with macro hygiene.  Though it's weird that it behaves
>> differently on
>> different systems.  Possibly different Java versionor different Kawa
>> versions (though
>> I don't recall changing anything in this area in a while).
>>
>> Could be a nice exercise to figure out for someone who
>> wants to understand how Kawa macro hygiene works.
>> --
>>         --Per Bothner
>> per@bothner.com   http://per.bothner.com/
>>
>

  reply	other threads:[~2021-09-14 18:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <971550055.197381511.1631259004148.JavaMail.root@zimbra65-e11.priv.proxad.net>
2021-09-10  7:33 ` phiroc
2021-09-14 12:42   ` Damien Mattei
2021-09-14 16:14     ` Philippe de Rochambeau
2021-09-14 16:34       ` Damien Mattei
2021-09-14 16:58         ` Philippe de Rochambeau
2021-09-14 17:26   ` Per Bothner
2021-09-14 17:38     ` Damien Mattei
2021-09-14 17:58     ` Damien Mattei
2021-09-14 18:00       ` Damien Mattei [this message]
2021-09-14 18:07         ` Per Bothner
2021-09-14 18:38           ` Damien Mattei
2021-09-14 19:30             ` Per Bothner
2021-09-15  7:10               ` phiroc
2021-09-16 10:02                 ` phiroc
2021-09-16 10:41                   ` Damien MATTEI
2021-09-16 11:05                     ` phiroc
2021-09-16 13:44                       ` Damien MATTEI
2021-09-17  5:29                       ` Per Bothner
2021-09-17  7:00                         ` phiroc
2021-09-17 10:48                           ` Per Bothner
2021-09-16 21:11                   ` Per Bothner

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='CADEOadcuxmR3Zp_thzjPY+A2rGTh+yFjJ62H-80f=8760F_iKg@mail.gmail.com' \
    --to=damien.mattei@gmail.com \
    --cc=jean-paul.roy@unice.fr \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    --cc=phiroc@free.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).