pointer and address

[yashwant pinge]

what does T*& oldmem means..?

[peter koch]

On 2 Apr., 13:29, "yashwant pinge" <yashwantpi...@ gmail.comwrote:

what does T*& oldmem means..?

Read from right to left: oldmem is a reference to a pointer to T. I
believe this one must be in the faq (if you don't have it, google for C
++ faq).

/Peter

[Alf P. Steinbach]

* yashwant pinge:

what does T*& oldmem means..?

It could be a valid function argument.

If it is, then oldmem is a reference to a pointer to T.

Include more context if you want more than such speculation.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[James Kanze]

On Apr 2, 1:35 pm, "Alf P. Steinbach" <[e-mail] rote:

* yashwant pinge:

what does T*& oldmem means..?

It could be a valid function argument.

Or a function return type, or a class member declaration, or a
local or global variable definition, or...

If it is, then oldmem is a reference to a pointer to T.

Include more context if you want more than such speculation.

It's true that if oldmem is a variable whose type overloads
operator& to return e.g. an int, and T is also a variable of
type int, the meaning changes. If the operators in the
expression aren't overloaded, however, I don't see what else it
could mean.

--
James Kanze (GABI Software) email:ja******* **@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientier ter Datenverarbeitu ng
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]

[alfps]

* James Kanze:

On Apr 2, 1:35 pm, "Alf P. Steinbach" <[e-mail] rote:

>* yashwant pinge:

>>what does T*& oldmem means..?

>It could be a valid function argument.

Or a function return type, or a class member declaration, or a
local or global variable definition, or...

>If it is, then oldmem is a reference to a pointer to T.

>Include more context if you want more than such speculation.

It's true that if oldmem is a variable whose type overloads
operator& to return e.g. an int, and T is also a variable of
type int, the meaning changes. If the operators in the
expression aren't overloaded, however, I don't see what else it
could mean.

I don't remember my thinking, but one situation when the meaning can
potentially change is, as you note, when it's an expression.

Also, consider "T*& oldmem() { ... }" ;-).

I think I just put in that about context because it's generally good
advice and the poster seemed to be unaware of the need for context.

--

You really should have this fixed.

Just to try it out I'm posting from Google groups.

If may signature delimiter is correct, then it should be possible for
anyone.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Alf P. Steinbach]

* alfps:

>
Just to try it out I'm posting from Google groups.

If may signature delimiter is correct, then it should be possible for
anyone.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

Dang! Google, you bad bad dog! Sit! Sit!

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?