Comparing literal empty strings in C

Question

In C, what is the following specified to do?

if ("" == "")
{
    printf("Empty strings are equal\n");
}

I have a compiler on hand that tells me that "" is indeed equal to "". But is this equality guaranteed?

Edit: I understand perfectly well how pointer comparison and string comparison work in C. What I'm asking is what behavior, if any, is specified in the C standard for compile-time constant empty strings. My belief is that the strings are not guaranteed to be equal, but in practice usually will be equal since all const empty strings will be interned to the same address. But I want to know if anyone can provide a definitive reference

It's not guaranteed to have equality. This has been discussed before on SO. — Sven Marnach
– Sven Marnach, Commented Apr 28, 2011 at 13:36
My belief is that the strings are not guaranteed to be equal, but in practice usually will be equal since all const empty strings will be interned to the same address. But I want to know if anyone can provide a definitive reference. — JSBձոգչ
– JSBձոգչ, Commented Apr 28, 2011 at 13:38
The C Standard says (6.4.5/6): "It is unspecified whether [string literals] are distinct". — pmg
– pmg, Commented Apr 28, 2011 at 13:41
@pmg, that's what I was looking for. Make it an answer and I'll accept it. — JSBձոգչ
– JSBձոգչ, Commented Apr 28, 2011 at 13:42

pmg · Accepted Answer · 2011-04-28 13:45:21Z

12

The C Standard says (6.4.5/6)

It is unspecified whether [string literals] are distinct

answered Apr 28, 2011 at 13:45

pmg

109k14 gold badges132 silver badges203 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Community · Accepted Answer · 2017-05-23 11:47:42Z

5

Guaranteed? I doubt it. You're not comparing the content of the strings but rather their addresses, which means that you're relying on the compiler to not emit two literal strings that happen to have the same content in the same location. It's likely to work, but not something you should rely on (nor is it clear what it's useful for).

Edit: See also Why is "a" != "a" in C? - it has an answer to basically the same question with nearly a hundred upvotes (and was written by a user whose compiler did it differently).

edited May 23, 2017 at 11:47

CommunityBot

11 silver badge

answered Apr 28, 2011 at 13:36

John Zwinck

252k44 gold badges346 silver badges459 bronze badges

1 Comment

SolarBear Over a year ago

John Zwinck is right, you're betting on the compiler's behavior. You should be using strcmp instead - unless, of course, you're REALLY interested in comparing addresses.

Glen · Accepted Answer · 2011-04-28 13:41:05Z

0

I don't think there is any guarantee that these will have the same address -- I doubt the standard would require such behavior. Why would you need to depend on this being predictable?

answered Apr 28, 2011 at 13:41

Glen

3352 silver badges10 bronze badges

Collectives™ on Stack Overflow

Comparing literal empty strings in C

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related