Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!news.iecc.com!nerds-end
From: torbenm@diku.dk (Torben Ægidius Mogensen)
Newsgroups: comp.compilers
Subject: Re: Thoughts on the JVM as a compilation Target?
Date: Tue, 29 May 2012 17:40:03 +0200
Organization: SunSITE.dk - Supporting Open source
Lines: 60
Sender: news@iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <12-05-027@comp.compilers>
References: <12-05-015@comp.compilers> <12-05-016@comp.compilers> <12-05-024@comp.compilers>
NNTP-Posting-Host: news.iecc.com
X-Trace: leila.iecc.com 1338306028 70162 64.57.183.58 (29 May 2012 15:40:28 GMT)
X-Complaints-To: abuse@iecc.com
NNTP-Posting-Date: Tue, 29 May 2012 15:40:28 +0000 (UTC)
Keywords: Java
Posted-Date: 29 May 2012 11:40:28 EDT
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
Xref: csiph.com comp.compilers:656

BGB <cr88192@hotmail.com> writes:


> maybe trying for a small list here:
> lack of unsigned operations;
> lack of pointers;
> lack of function or method references;
> lack of variable references (need not be pointers);
> lack of a lexical environment;
> lack of good dynamic types;
> lack of package-scoped declarations;
> lack of operators over object types;
> lack of pass-by-value / structure types;
> lack of RAII or similar;
> lack of a good C FFI.

A few more:

 - Lack of proper tail calls.

   This can be implemented using trampolines, but this is inefficient
   and kludgy.  Scala (AFAIR) implements only tail recursion and not
   proper tail calls because of this limitation.

 - Lack of non-nullable reference types.

   Object/reference types are implicitly always nullable, though it is
   simple to statically verify non-nullable types.  The consequence is
   that the VM always has to check for null pointers when following
   references, even when the reference can never be to null.

 - Lack of structural type equivalence.

   This means that you have to resort to kludges when implementing pair
   types and similar structures, and it gives problems when implementing
   (type-safe) polymorphic pair types.  Which leads to

 - Lack of parametric polymorphism.

   Generics is currently implemented with type erasure to Object and
   (runtime-checked) downcasts, which is inefficient.  Statically
   verified parametric polymorphism could avoid this.

 - Lack of an unbounded integer type.

   Though this can be implemented using JVM primitives, it is slow and
   kludgy to do so.  Many languages (Scheme, Haskell, ...) have
   unbounded integers.

 - Inefficient exception handling.

   This was a real limitation for some students that tried to implement
   a subset of Prolog in JVM.  Exceptions were the natural way to
   implement cut (!), but it was just way too slow.

This is what I could think off at the top of my head, but I'm sure more
would come up if I tried to use JVM as target for a realistically-sized
language (as opposed to toy languages).

	Torben