Re: Teaching new tricks to an old dog (C++ -->Ada)
Date: Fri, 11 Mar 2005 17:34:17 -0500
Pascal Obry wrote:
> That's not a misunderstanding. That's how Sun has described Java. They started
> from C++ and have removed many unsafe features. They eventually stop the
> process at some point and this has given birth to Java. That's history.
Although in at least one point they removed something that
Ada had already proved is not necessarily unsafe: operator
overloading. As a result, Java programmers either have to
give up both object-orienting and abstraction or use crap like
for things that are conceptually numeric.
If you put garbage in a computer nothing comes out but garbage.
But this garbage, having passed through a very expensive machine,
is somehow ennobled and none dare criticize it.
- Re: Optimise my ray tracer
... My Java implementation of the ray tracer is slow because I represented 3D ... garbage collection and functional programming style. ... collected languages, it is a shame that comparable performance can only be ...
- Re: Allocation outside garbage-collected heap
... > use those objects in Java I need to allocate it using AllocObject ... if you want to use it as an object in java you do. ... there are definitely applications where current java garbage ...
- Re: A re-announce on GCs defects
... GC is worthless garbage? ... That must be why Java was a flash in the pan. ... general conclusion is fair game: for a memory management method that is ... you can draw: ...
- Re: Teaching new tricks to an old dog (C++ -->Ada)
... That's how Sun has described Java. ... > process at some point and this has given birth to Java. ... If you put garbage in a computer nothing comes out but garbage. ...
- Re: how many objects r eligible for garbage Collection ?
... Java 6 does collect objects where the only references have no further use. ... It is possible to observe this behaviour if you also have a weak reference to the 'garbage'. ... public void add(boolean nullify, boolean gc, boolean sleep) ...