Re: Ada and Java. different behaviour. casting long to int problem.

["David Botton" <David@Botton.com>]

AdaMagic already does the interfaces (see Tucker Taft's paper on it and
examples in the Ada bindings to the JDK) and I am willing to sacrifice a
little more typing now for long term maintenance, cross platform code (YES,
JVM is just another platform to Ada), flexible package structure, type
safety, tasking and protected types (soon in JGNAT), specs and bodies,
separate compiled bodies, child packages, etc. etc. etc. (Insert here just
about every improvement Ada has over C and C++ and throw it in here). I find
that even on the JVM Ada is more readable then Java. Ada was written for the
maintainer not the programmer.

I find that my code is not overly cluttered and as Ada frameworks are built
to abstract the JDK API, I think that even those with a bias will find Ada
to be far easier reading.

There is no benefit to use Java over Ada on the JVM  for Software
Engineering. There are areas where Java will excel over Ada on the JVM, but
programming in the large and anything requiring reliable correct code isn't
one of them.

Java is C on the JVM with a little less flexibility.

BTW, does any one know of a JVM written in Java?

David Botton


Dale Stanbrough wrote in message ...
>David Botton wrote:
>
>" AdaMagic and OA are already doing it for most of Ada now (missing tasks
and
>  protected types, although they can be emulated using JDK calls)"
>
>
>...but i think that Java is easier to read in some circumstances. You don't
>end up having the code cluttered up with ".all", "'access" and "access".
>
>I also like Java's interfaces, a feature I'm not sure how Ada can
replicate.
>
>
>Dale