From: Adam Flinton 

Ellen K. wrote:
> ISTR (but don't everyone jump on me if this is wrong, I am no Java
> expert) that in Java the "native" datatypes like an integer go on the
> stack, while the object ones go on the heap.   But even without that
> obviously the native datatypes are gonna be faster to work with.
>

int.

integer is an object.

Adam

> On Mon, 8 Nov 2004 18:44:32 -0600, "Geo"
 wrote in
> message :
>
>
>>"Antti Kurenniemi" 
wrote in message
>>news:418fa68a$1{at}w3.nls.net...
>>
>>>"Geo"  wrote in message
news:418f51bf{at}w3.nls.net...
>>>
>>>>"Peter Sawatzki"  wrote in message
>>>>news:MPG.1bf827b322d0373989741{at}news.barkto.com...
>>>>
>>>>
>>>>>The main difference is that functions that operate on a class are
>>>>>implicitly called with the self/this pointer as an invisible
>>
>>"argument".
>>
>>>>Why is that distinction important?
>>>
>>>You can toss an object (an instance of a class) to other functions /
>>
>>objects
>>
>>>as a parameter, which you can't do with a main() and a bunch of other
>>>separate functions. That's one that comes to mind immediately.
>>
>>Ok but that doesn't explain what the difference between a data type like
>>"int" and a class like "Date" is.
>>
>>Geo.
>>
>
>

--- BBBS/NT v4.01 Flag-5