From: "Peter" <craven@gmx.net>
To: kawa mailing list <kawa@sourceware.org>
Subject: Re: Problems with old kawa android code
Date: Tue, 08 Dec 2020 10:10:54 +0100 [thread overview]
Message-ID: <875z5cu0gx.fsf@nexoid.at> (raw)
In-Reply-To: <b04afaeb-3fcc-6d86-64db-ff5172904e3a@bothner.com>
> Short answer:
> The simplest fix is probably to remove
> (require 'android-defs)
> and add whatever aliases you need.
Thanks, this worked well!
I've run into another (probably unrelated to Android) problem:
I use an anonymous subclass of android.os.AsyncTask, which has a
function:
protected final void publishProgress (Progress... values)
If I just use publishProgress directly, kawa complains that no such slot
exists, but if I just define-simple-class the subclass (making it
non-anonymous), things work fine.
Is it possible that there's a bug with anonymous subclasses and
protected and/or final functions?
Thanks a lot for your help with this!
Greetings, Peter
prev parent reply other threads:[~2020-12-08 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 21:28 Peter
2020-12-08 1:22 ` Per Bothner
2020-12-08 9:10 ` Peter [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=875z5cu0gx.fsf@nexoid.at \
--to=craven@gmx.net \
--cc=kawa@sourceware.org \
/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).