This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: Problem defining a class implementing an interface nested in a class
- From: Moritz Heidkamp <moritz at twoticketsplease dot de>
- To: Per Bothner <per at bothner dot com>
- Cc: kawa at sourceware dot org
- Date: Mon, 28 Feb 2011 13:39:10 +0100
- Subject: Re: Problem defining a class implementing an interface nested in a class
- References: <87zkphce1k.fsf@twoticketsplease.de> <4D6B0240.5000802@bothner.com>
Hi Per,
Per Bothner <per@bothner.com> writes:
> On a modern JVM like HotSpot there should be very little "JVM overhead"
> - except for start-up time, which is certainly an issue.
right, I am mainly referring to the start-up time which keeps me from
using JVM based languages for my everyday programming needs. But on the
JVM, Kawa is certainly my first choice now.
> For now you have to use JVM "internal" class names:
>
> javax.swing.text.AbstractDocument$Content
Thank you, too!
> The name javax.swing.text.AbstractDocument is actually a single
> identifier, not a compound expression.
>
> It could be possible for Kawa to automatically map
> javax.swing.text.AbstractDocument.Content to
> javax.swing.text.AbstractDocument$Content. Maybe later.
Yeah, I'm familiar with Scheme's syntax but figured that Kawa handles
these symbols in a special way. The mapping would certainly help Java
novices like me :-)
Thanks again guys!
Moritz