Glen Cole wrote:
Gavin <[log in to unmask]> wrote:
>> There are now three *released* Java integrated development environments
>> for the Mac, where there were none a month ago.
>
>Those are the ones from Natural Intelligence, Symantec, and... Metrowerks?
>Metrowerks *has* released "Discover Programming with Java," but
>CodeWarrior 9 (Object Pascal, C/C++, Java) is scheduled to ship May 15th.
 
Metrowerks, yes, based on their Press release of Monday.
 
>Does the Discover book include *full* Java support, or is it a "lite"
>version like most other language books that include a CD-ROM? (For that
>matter, I think the Discover series is *only* CD-ROM -- no paper.)
 
I've never seen a Metrowerks product that was *more* than just a CD-ROM,
although they seem to be putting them in boxes at least nowadays.
 
Discover Programming with Java is supposed to be a *full* development
environment.  It sounds from the press release and info at www.metrowerks.com
that it is about equivalent to Symantec's Cafe.  It appears to support
both PPC and 680x0 Macs.  Symantec's Cafe for the Mac is (as of last night at
least) PPC only, but is supposed to get a patch for 680x0 support any day now.
I think both products sell for $99.  Cafe can be purchased online and downloaded
over the net.
 
>> because [Java] has no Pointers, no #include files, and no preprocessor,
>
>Ummm, begging the Colonel's pardon (sorry, the theme to "Go Go Gophers"
>just popped in), but while there is no "#include" per se, doesn't
>"import" qualify as a replacement? (Not to imply that the function
>is identical, mind you, or that the sheer number of "import" statements
>approaches that of "#include"...)
 
The Java 'import' statement simply makes it easier to type names.  It
"imports" names of classes out of the package hierarchy into the local
namespace.  The statement:
 
import java.util.Hashtable;
 
simply lets you refer to the class as "Hashtable".  Without this statement
you could still use Hashtables, you would just have to type their full name
all the time such as:
 
  void myMethod foo() {
    int i;
    java.lang.Hashtable myHash = new java.lang.Hashtable();
 
rather than the simpler:
 
    Hashtable myHash = new Hashtable();
 
so 'import' does not "replace" anything.  It's just a naming shortcut.
 
>I must be tired; this is looking too much like rambling.
>Must get some sl.....zzzzzzz
 
Group, Public or System?
 
G.