From: Helmut Eller <eller.helmut@gmail.com>
To: kawa@sourceware.org
Subject: Re: The Expression problem
Date: Wed, 31 Aug 2022 09:13:44 +0200 [thread overview]
Message-ID: <m2v8q8997b.fsf@gmail.com> (raw)
In-Reply-To: <d744ae3b-cdf5-67a4-3f31-f4c254ffa4a0@bothner.com>
> I think Common Lisp generics are problematic if you have a module system
> (or library system to use R7RS terminology) based on static name resolution.
> CL generics assume a generic function is global, and as each module is loaded
> it dynamically adds methods to the generic procedure. This is powerful,
> but seems contrary to modern module system. I've thought a bit about
> how best to
> specify multi-methods in a more disciplined way. It's not an easy problem.
I'm not sure what this has do with static name resolution specifically,
but I note that the Julia language seems to be somewhat successful
(ie. popular) with multi-methods that aren't all that different from
Common Lisp's generic functions.
It also seems me that the team behind the Fortress language tried pretty
hard to come up with a static type system for multi-methods. They made
some progress, but in the end they failed.
I think that for Kawa a Julia-style approach would be "good enough".
Especially, as one can use Java interfaces in places where static typing
is a concern.
Helmut
prev parent reply other threads:[~2022-08-31 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 21:35 daniel szmulewicz
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 [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=m2v8q8997b.fsf@gmail.com \
--to=eller.helmut@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).