From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa <kawa@sourceware.org>
Subject: Re: A problem with interfaces
Date: Wed, 20 Dec 2023 00:24:23 +0100 [thread overview]
Message-ID: <CAMFYt2ZkNB6_d-PY=1GxVmFnFfb8=JKuo=qG6RzqZV32i01z+A@mail.gmail.com> (raw)
In-Reply-To: <68438f29-d0ad-4eac-88b9-50fefb329827@bothner.com>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
I think that isolating the bug could be a bit difficult at the moment,
but I might try that later (I feel that this would require a lot of work,
and I'm not sure if I would succeed at the end)
But I did publish the breaking change, in case you'd want to have a look
https://github.com/panicz/grasp/commit/c678761a788a0356c3ecd1caa9f2c7a8bc900f57
(if running with the X server available, it's best to run ./grasp-desktop,
because
all the diagnostic messages go to console But since the program just dies,
running ./grasp-terminal should also be OK. Running ./run-tests 3 also
reproduces
the bug)
wt., 19 gru 2023 o 23:46 Per Bothner <per@bothner.com> napisał(a):
>
>
> On 12/19/23 14:23, Panicz Maciej Godek via Kawa wrote:
> > But when I do this, the system claims that Atom is not Extensive (even
> > though it implements a sub-interface of the Tile interface). How could
> that
> > be?
> I don't know - could be a bug. There hasn't been a lot of testing of
> interfaces
> defined this way.
>
> If you can create a short (20 lines or so) self-contained test-case,
> I can take a look. It might turn out to be a simple problem.
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
>
prev parent reply other threads:[~2023-12-19 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 22:23 Panicz Maciej Godek
2023-12-19 22:46 ` Per Bothner
2023-12-19 23:24 ` Panicz Maciej Godek [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMFYt2ZkNB6_d-PY=1GxVmFnFfb8=JKuo=qG6RzqZV32i01z+A@mail.gmail.com' \
--to=godek.maciek@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).