"new" keyword on value and object types?

I'm curious about the differeng behavior of the "new" keyword when dealing
with value versus object types. If I'm correct, when I do:

dim x as integer

There's no need for "new" to be called since this "value" type is all set to
go. Is this because value types are stored on the stack so the memory
initialization is already taken care of?

Now, when dealing with an object type, it seems you do need to use the "new"
keyword. Accordingly, when I do:

dim x as oledbconnection

What exactly is x before it's assigned to something with the "new" keyword?
Is it just space on the stack just as before?

Assuming this all to be the case, I'm curious about the behavior of the
String class. I was under the impression that it is not a value type.
However, it can be assigned to without using the new keyword, which breaks
the logic I thought applied. Further, it allows you to use the new keyword on
it.

Another question: What is the purpose of the "new" keyword on a value type?
Is it just for initialization (calling a constructor)? When "new" is called
on a object type, does it do this as well as return a pointer to the heap
address?

Thanks for any clarification...

-Ben

re: "new" keyword on value and object types?

[color=blue]
>Is this because value types are stored on the stack[/color]

Value type variables aren't always stored on the stack, that's only
true for local variables.

[color=blue]
>initialization is already taken care of?[/color]

All variables in VB are initialized to their default values. The
default value is basically when all bits are set to zero. That means
zero for numeric types, False for booleans and Nothing for reference
type variables.

[color=blue]
>Now, when dealing with an object type, it seems you do need to use the "new"
>keyword.[/color]

Only to assign something other than a Nothing reference (which you
probably want to do something useful with the variable).

[color=blue]
>What exactly is x before it's assigned to something with the "new" keyword?[/color]

Nothing

[color=blue]
>Is it just space on the stack just as before?[/color]

If it's a local variable, there's space allocated on the stack for it
yes.

[color=blue]
>Assuming this all to be the case, I'm curious about the behavior of the
>String class. I was under the impression that it is not a value type.[/color]

Right, it's a reference type.

[color=blue]
>However, it can be assigned to without using the new keyword, which breaks
>the logic I thought applied. Further, it allows you to use the new keyword on
>it.[/color]

When you use a string literal a String object is implicitly created
for you so you don't have to write New.

[color=blue]
>Another question: What is the purpose of the "new" keyword on a value type?
>Is it just for initialization (calling a constructor)?[/color]

Yes.


Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

re: "new" keyword on value and object types?

>Value type variables aren't always stored on the stack, that's only
true for local variables.

Could you give an example of when a value type is not stored on the stack?
Is it in the case of a class member? If so, does it matter if it's static?
[color=blue][color=green]
> >Another question: What is the purpose of the "new" keyword on a value type?
> >Is it just for initialization (calling a constructor)?[/color]
>
> Yes.[/color]

So to confirm, when using "new" on a reference type, it does two things: 1)
It calls the appropriate constructor and 2) it returns the address of the
object on the heap for the assignment to the reference type variable. In the
case of calling new on a value-type variable, calling new does call the
appropriate constructor but returns nothing. Is this correct?

Is this separation of "reference" and "value" types different from classes
versus structs (object vs. value types)? Can you always conclude that a
struct is a value type and a class is a reference type?

Thanks for your helpful info, Mattias...

-Ben


"Mattias Sjögren" wrote:
[color=blue]
>[color=green]
> >Is this because value types are stored on the stack[/color]
>
> Value type variables aren't always stored on the stack, that's only
> true for local variables.
>
>[color=green]
> >initialization is already taken care of?[/color]
>
> All variables in VB are initialized to their default values. The
> default value is basically when all bits are set to zero. That means
> zero for numeric types, False for booleans and Nothing for reference
> type variables.
>
>[color=green]
> >Now, when dealing with an object type, it seems you do need to use the "new"
> >keyword.[/color]
>
> Only to assign something other than a Nothing reference (which you
> probably want to do something useful with the variable).
>
>[color=green]
> >What exactly is x before it's assigned to something with the "new" keyword?[/color]
>
> Nothing
>
>[color=green]
> >Is it just space on the stack just as before?[/color]
>
> If it's a local variable, there's space allocated on the stack for it
> yes.
>
>[color=green]
> >Assuming this all to be the case, I'm curious about the behavior of the
> >String class. I was under the impression that it is not a value type.[/color]
>
> Right, it's a reference type.
>
>[color=green]
> >However, it can be assigned to without using the new keyword, which breaks
> >the logic I thought applied. Further, it allows you to use the new keyword on
> >it.[/color]
>
> When you use a string literal a String object is implicitly created
> for you so you don't have to write New.
>
>[color=green]
> >Another question: What is the purpose of the "new" keyword on a value type?
> >Is it just for initialization (calling a constructor)?[/color]
>
> Yes.
>
>
> Mattias
>
> --
> Mattias Sjögren [MVP] mattias @ mvps.org
> http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
> Please reply only to the newsgroup.
>[/color]

re: "new" keyword on value and object types?

Ben,
[color=blue]
>Could you give an example of when a value type is not stored on the stack?
>Is it in the case of a class member?[/color]

Yes exactly. Or when you have an array of the value type.

[color=blue]
>If so, does it matter if it's static?[/color]

No

[color=blue]
>So to confirm, when using "new" on a reference type, it does two things: 1)
>It calls the appropriate constructor and 2) it returns the address of the
>object on the heap for the assignment to the reference type variable. In the
>case of calling new on a value-type variable, calling new does call the
>appropriate constructor but returns nothing. Is this correct?[/color]

Yes that sounds right. Since the space for the value type variable is
already allocated there's no need to return a pointer to any newly
allocated object. You just overwrite the existing space.

[color=blue]
>Is this separation of "reference" and "value" types different from classes
>versus structs (object vs. value types)?[/color]

Reference types include classes (including delegates) and interfaces.
Value types include structs and enums.

[color=blue]
>Can you always conclude that a
>struct is a value type and a class is a reference type?[/color]

Yes


Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

re: "new" keyword on value and object types?

Hi Ben,

I think mattias has given you a detailed reply. Do you have any concern on
this issue? Please feel free to tell me, thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.