public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: Building for Android
Date: Fri, 21 Oct 2022 21:45:21 +0200	[thread overview]
Message-ID: <CAMFYt2Y3gU9ZZrLYbNYF_3Ad9TyMzuRE7ZaqMZrwC8TXpsO6nQ@mail.gmail.com> (raw)
In-Reply-To: <b1ee1d93-690f-4687-59e4-5e9eb454f610@bothner.com>


[-- Attachment #1.1: Type: text/plain, Size: 677 bytes --]

Attached.

During its compilation, Kawa issues the following warning:

subclass-refering-to-mangled-superclass-property.scm:6:4: warning - no
declaration seen for mangled-name

pt., 21 paź 2022, 21:31 użytkownik Per Bothner <per@bothner.com> napisał:

>
>
> On 10/21/22 12:19, Panicz Maciej Godek wrote:
>
> > However, the issue with accessing superclass properties with mangled
> names from a subclass remains unsolved.
>
> Can you come up with a test-case that doesn't require Android,
> but fails if you force USE_SYMBOLIC to force?  Comment out the /* #ifdef
> */ etc.
>
> --
>         --Per Bothner
> per@bothner.com   http://per.bothner.com/
>

[-- Attachment #2: subclass-refering-to-mangled-superclass-property.scm --]
[-- Type: application/octet-stream, Size: 156 bytes --]

(define-simple-class SuperClass ()
  (mangled-name ::boolean init: #f))

(define-simple-class SubClass (SuperClass)
  ((*init*)
   (set! mangled-name #t)))

  reply	other threads:[~2022-10-21 20:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 14:57 Panicz Maciej Godek
2022-10-18 15:25 ` Per Bothner
2022-10-18 18:25   ` Panicz Maciej Godek
2022-10-19  9:15     ` Panicz Maciej Godek
2022-10-19 16:05       ` Per Bothner
2022-10-19 17:09         ` Panicz Maciej Godek
2022-10-20  5:35           ` Panicz Maciej Godek
2022-10-20 20:48             ` Panicz Maciej Godek
2022-10-21  5:14               ` Panicz Maciej Godek
2022-10-21 13:59                 ` Panicz Maciej Godek
2022-10-21 18:11                   ` Per Bothner
2022-10-21 19:19                     ` Panicz Maciej Godek
2022-10-21 19:31                       ` Per Bothner
2022-10-21 19:45                         ` Panicz Maciej Godek [this message]
2022-10-21 20:13                           ` Panicz Maciej Godek
2022-10-22  6:26                           ` Per Bothner
2022-10-22  9:31                             ` Panicz Maciej Godek
2022-10-22 12:08                               ` Panicz Maciej Godek
2022-10-24  7:22                                 ` Panicz Maciej Godek
2022-10-24 10:48                                   ` Per Bothner
2022-10-24 12:01                                     ` Panicz Maciej Godek
2022-10-21 18:00           ` 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=CAMFYt2Y3gU9ZZrLYbNYF_3Ad9TyMzuRE7ZaqMZrwC8TXpsO6nQ@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).