Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news-1.dfn.de!news.dfn.de!news.informatik.hu-berlin.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: v_borchert@despammed.com (Volker Borchert) Newsgroups: comp.lang.java.programmer Subject: Re: Alternatives languages on the JVM: which one or is there no alternative? Date: 26 Nov 2013 21:28:13 GMT Organization: Private site at Eddersheim, Germany Lines: 17 Distribution: world Message-ID: References: X-Trace: individual.net 6PFm9oDu0E7bKlyZXWDuUwWtEdRBZCUxAVEdGmZL5WgCiGRBhK Cancel-Lock: sha1:UNepmZP+QQlcHjz0i30OYbDfDjo= Xref: csiph.com comp.lang.java.programmer:26627 No language that is to run on the JVM can overcome its fundamental shortcoming of missing multiple implementation inheritance. While this might not be a problem with everyday code, is _is_ a problem if you are in low-level or framework stuff, for example if you have class hierarchies where you want to offer mixed reference flavors - your class C either ends up with two fields, one T and one to some (X extends WeakReference) which contains another extra field for the back reference to the containing C so that the C can be notified of the X having been garbage collected and an extra two-word object header, or with lots of duplicated code. -- "I'm a doctor, not a mechanic." Dr Leonard McCoy "I'm a mechanic, not a doctor." Volker Borchert