Names, Binding , Type Checking, and

[Salsafc]

Take three of your chosen programming languages( C , C ++ and Java) and compare and contrast them on the following perspectives:-
• Type binding
• Storage binding
• Type Checking

[sicarie]

Take three of your chosen programming languages( C , C ++ and Java) and compare and contrast them on the following perspectives:-
• Type binding
• Storage binding
• Type Checking

That's a statement. Do you have a question about one of those points?

(Please keep in mind the FAQ - we cannot and will not do your homework for you - but we are more than happy to help you find resources through which you can answer the question)

[Salsafc]

That's a statement. Do you have a question about one of those points?

(Please keep in mind the FAQ - we cannot and will not do your homework for you - but we are more than happy to help you find resources through which you can answer the question)

can explain to me storage binding for c c++ and java..compare them..i cant find any source

[sicarie]

can explain to me storage binding for c c++ and java..compare them..i cant find any source

No, as I said, I will not do your homework for you.

But I will help you with this, if you are willing to do work. What google searches have you done to try to figure these out?

[Salsafc]

No, as I said, I will not do your homework for you.

But I will help you with this, if you are willing to do work. What google searches have you done to try to figure these out?

For C

- uses the key word static to define a variable as static


-local variables are by default, stack-dynamic, and are called “automatic” and declared as ‘auto’


Heap-dynamic variables
- variables are created by a call to a system subprogram


For c++


- local variables are by default, stack-dynamic, and are called “automatic” and declared as ‘auto’

- variables are created by an operator


For java

- variables are created by an operator

[sicarie]

For C

- uses the key word static to define a variable as static


-local variables are by default, stack-dynamic, and are called “automatic” and declared as ‘auto’


Heap-dynamic variables
- variables are created by a call to a system subprogram


For c++


- local variables are by default, stack-dynamic, and are called “automatic” and declared as ‘auto’

- variables are created by an operator


For java

- variables are created by an operator

Ok, you have a good start there - where do you need help?

[Salsafc]

Ok, you have a good start there - where do you need help?

C and java is stack dynamic for storage binding..how about c ++ huh?

[Salsafc]

local variables are by default, stack-dynamic, and are called “automatic” and declared as ‘auto’

this statement true for java huh?? its true for c n c++..

[sicarie]

local variables are by default, stack-dynamic, and are called “automatic” and declared as ‘auto’

this statement true for java huh?? its true for c n c++..

I'm sorry, I don't know that much about memory management in Java. I started in C++ worrying about memory and everything, and it's one of the things I gave up when I started learning Java.

Maybe one of our other cross-forum posters can comment on that?

[RedSon]

For c/c++ variables and objects declared in the local scope are saved in the stack. For heap allocations you have to declare them (correct me if I am wrong) statically or globally (or both) or with a memory management function.