True and False problems
TRUE/FALSE
1. You can initialize a pointer variable by applying the operator * to an existing variable of an appropriate type.
2. By using cin.get(), you can read ‘\n’ as a character.
3. Explicit constructor call returns a reference of an anonymous object of the corresponding class.
4. A dynamic variable should not be pointed by more than one pointer variables.
5. An object of a class A can be a private member of a class B.
6. Static member variables of a class can be modified by non-static member functions of that class.
7. A friend function of a class should not be overloaded to support automatic type conversion.
8. A function can return the name of an array by using the ‘return by reference’ mechanism.
9. You can’t have a private member variable of a certain name, when there already exists a public member variable of the same name.
10. Dangling pointers occur when the memory used by dynamic variables is not properly returned to the freestore (i.e., heap).
could you help me with the answers plz
1. You can initialize a pointer variable by applying the operator * to an existing variable of an appropriate type.
2. By using cin.get(), you can read ‘\n’ as a character.
3. Explicit constructor call returns a reference of an anonymous object of the corresponding class.
4. A dynamic variable should not be pointed by more than one pointer variables.
5. An object of a class A can be a private member of a class B.
6. Static member variables of a class can be modified by non-static member functions of that class.
7. A friend function of a class should not be overloaded to support automatic type conversion.
8. A function can return the name of an array by using the ‘return by reference’ mechanism.
9. You can’t have a private member variable of a certain name, when there already exists a public member variable of the same name.
10. Dangling pointers occur when the memory used by dynamic variables is not properly returned to the freestore (i.e., heap).
could you help me with the answers plz
http://cplusplus.com/forum/general/22615/
Please don't post the same crap multiple times. You're not helping your case here.
EDIT:
Also...
As a wise man once said... if you type "plz" because it's shorter than "please", then I'll type "no" because it's shorter than "yes".
=P
Please don't post the same crap multiple times. You're not helping your case here.
EDIT:
Also...
| could you help me with the answers plz |
As a wise man once said... if you type "plz" because it's shorter than "please", then I'll type "no" because it's shorter than "yes".
=P
Last edited on
@Disch: Win.
@waxth: Just put in TRUE for all of them. You have a 50/50 chance of getting it right. Or, if you don't want to do that, check your "first" tread.
-Albatross
@waxth: Just put in TRUE for all of them. You have a 50/50 chance of getting it right. Or, if you don't want to do that, check your "first" tread.
-Albatross
| 1. You can initialize a pointer variable by applying the operator * to an existing variable of an appropriate type. |
This one looks like a trick question...
closed account (S6k9GNh0)
Let me consult the problem here. We do not appreciate those that don't want to even try something we enjoy doing on an everyday basis. If it were simply a tedious task that would be easier and not educational, the case might be different. These questions are very simplistic, and I can solve them without any reference in a couple of minutes.
Take the thirty minutes to actually do the work for once, and you might find it enjoyable to actually understand it.
I'd also like to mention that if your doing this because your due date is up, then your an idiot and you deserve not to be helped. I hate people who procrastinate and then beg for others to help.
Take the thirty minutes to actually do the work for once, and you might find it enjoyable to actually understand it.
I'd also like to mention that if your doing this because your due date is up, then your an idiot and you deserve not to be helped. I hate people who procrastinate and then beg for others to help.
For future reference: If you find reading explanations too hard, how about trying to feed a compiler with those questions? Trying it out yourself is the quickest way to find out how something works (or rather, what happens when you do it. The "how" is usually a bit more complex than the "what").
Topic archived. No new replies allowed.