public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: daniel szmulewicz <daniel.szmulewicz@gmail.com>
To: kawa@sourceware.org
Subject: The Expression problem
Date: Tue, 30 Aug 2022 00:35:58 +0300	[thread overview]
Message-ID: <CAABPU6_r4hZq+rN_DdEvwdJ-43ZTsGRVTYqWqWkhvziuf5yQEw@mail.gmail.com> (raw)

Hi,

I was wondering what was Kawa's stance regarding the Expression problem,
ie. extending existing Java classes.
ABCL provides a mechanism to specialize on Java classes as documented in
section 4.5.2 of the user manual. Clojure provides defprotocol and defmulti
to extend existing types. I skimmed through the Kawa manual and am still
unsure. I am very curious to hear more from the experts.

Thank you.

Daniel

WARNING: multiple messages have this Message-ID

From: daniel szmulewicz <daniel.szmulewicz@gmail.com>
To: kawa@sourceware.org
Subject: The Expression problem
Date: Tue, 30 Aug 2022 00:35:58 +0300	[thread overview]
Message-ID: <CAABPU6_r4hZq+rN_DdEvwdJ-43ZTsGRVTYqWqWkhvziuf5yQEw@mail.gmail.com> (raw)
Message-ID: <20220829213558.vU366AO5IAoawMnBfx8k2bmDEMGtcwXYeSiHl6XZFxM@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 414 bytes --]

Hi,

I was wondering what was Kawa's stance regarding the Expression problem,
ie. extending existing Java classes.
ABCL provides a mechanism to specialize on Java classes as documented in
section 4.5.2 of the user manual. Clojure provides defprotocol and defmulti
to extend existing types. I skimmed through the Kawa manual and am still
unsure. I am very curious to hear more from the experts.

Thank you.

Daniel

             reply	other threads:[~2022-08-29 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 21:35 daniel szmulewicz [this message]
2022-08-29 21:35 ` daniel szmulewicz
2022-08-29 22:11 ` Per Bothner
2022-08-30 18:24   ` daniel szmulewicz
2022-08-30 18:24     ` daniel szmulewicz
2022-08-30 18:57     ` Per Bothner
2022-08-30 18:57       ` Per Bothner
2022-08-31  7:13       ` Helmut Eller

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=CAABPU6_r4hZq+rN_DdEvwdJ-43ZTsGRVTYqWqWkhvziuf5yQEw@mail.gmail.com \
    --to=daniel.szmulewicz@gmail.com \
    --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).