[LINK] REAL Basic language for Win, Mac and Linux

[Adam Neat]

<snip>

> 
> Potential licencing problems aside, no-one has raised the O-O problems
> with Java, so I may as well list the few I have come across.
> 
> WARNING: techno-babble ahead!
> 
> 1. Timely destruction of objects at end of scope is *not* guaranteed.
> 
>     Every other O-O language I know of does guarantee this (possibly VB
>     excepted). If you teach students the constructor/destructor paradigm
>     in Java, they are learning the wrong thing and produce the wrong code.
>     In the enterprise I have seen horrible hacks to get around this
>     "problem", although when I've approached Java programmers about this,
>     they don't even know it is a problem. They have learned to code O-O
>     incorrectly.
> 
> 2. Containers only hold base class objects; up-casting is required to
>     extract, say, a Person object from a list. This is plain wrong. And
>     it is often called the 'goto' of data. Run-time excpetions anyone?
>     Other lanugages do not have this problem AFAIK, although O-O Pascal
>     can be messy in this regard as well.
> 
> 3. No support for generic programming, so-called templates. A good O-O
>     language either supports dynamic typing or genericity or both. Java
>     provides neither.
> 

Gordon many of these have been resolved in Java Tiger (aka Java 5, nee 1.5).

<snip>

> 
> Unlink, anybody?
> 

*nods*

-------------------------------------------------
Adam Neat | Melbourne, Australia
email:  adamneat at anoti.com   
msn:    adamneat_ at hotmail.com
web:    http://www.anoti.com/adamneat/
-------------------------------------------------