Difference

[mmgis]

Dear all,

Can some body explain the difference between

Basemap* basemap

and

Basemap *basemap


Thanks in advance

[Peter87]

The meaning is exactly the same.

[E0p9LyTq]

Basemap* basemap is the same as

Basemap * basemap is the same as

Basemap *basemap

[Naughty Albatross]

Basemap* basemap
and
Basemap *basemap

They are just exactly the same.

Did you mean this :
Basemap* basemap
and
Basemap *basemap2

???

[mmgis]

Did you mean this :
Basemap* basemap
and
Basemap *basemap2


Query:what makes the difference?
Is the two instance [basemap & basemap2] are created for the class Basemap?

[48T7M4Gy]

It's also the same as Basemap*basemap

[mmgis]

Dear All,

Thanks for the replies.

MMGIS

[geeloso]

Am I missing something here??!

[TheIdeasMan]

https://isocpp.org/wiki/faq/style-and-techniques#whitespace

For C++ they recommend Basemap* basemap because it emphasises the type.

[48T7M4Gy]

I agree as it's clearer to me but the bottom line is it doesn't matter. Here's another authority.

Is ``int* p;'' right or is ``int *p;'' right?

http://www.stroustrup.com/bs_faq2.html#whitespace

[Peter87]

It doesn't matter for the compiler but it might matter to people.

[48T7M4Gy]

It doesn't matter for the compiler but it might matter to people.

Well read, that's exactly what Stroustrup says with his usual impeccable logic and advice.

[E0p9LyTq]

TheIdeasMan wrote:

For C++ they recommend Basemap* basemap because it emphasises the type.

With that emphasis on type declaring multiple variables on a single line can cause problems.

int* p1, p2; // error!

p1 is a pointer to an int, p2 is just a POD int. Variables should always be declared on separate lines.

int* p1;
int  p2;

Readability is for us humans, the compiler doesn't need all the whitespace and extra lines.

[JLBorges]

> declaring multiple variables on a single line can cause problems.

The critical confusion comes (only) when people try to declare several pointers with a single declaration:
int* p, p1; // probable error: p1 is not an int*

Placing the * closer to the name does not make this kind of error significantly less likely.
int *p, p1; // probable error?

Declaring one name per declaration minimizes the problem - in particular when we initialize the variables. People are far less likely to write:

	int* p = &i;
	int p1 = p;	// error: int initialized by int* 

And if they do, the compiler will complain.

Stroustrup - http://www.stroustrup.com/bs_faq2.html#whitespace

[48T7M4Gy]

Whenever something can be done in two ways, someone will be confused.

Whenever something is a matter of taste, discussions can drag on forever.

Stick to one pointer per declaration and always initialize variables and the source of confusion disappears.

Stroustrup - http://www.stroustrup.com/bs_faq2.html#whitespace

... now flogged to a standstill.
http://idioms.thefreedictionary.com/flog+to+death