Peter Annema wrote:
> I think the order is undefined, so you might end up with LMY_STRING,
> where ## won't help. However, iirc we are currently doing it in our code
> in a few places, and all seems to be fine (maybe we're just lucky).
I believe it is correct, because of ## being within NS_L:
NS_NAMED_LITERAL_STRING gets expanded, which yields
NS_NAMED_MULTILINE_LITERAL_STRING(kMyString,NS_L("strings are hard"))
Which then yields
NS_NAMED_MULTILINE_LITERAL_STRING(kMyString,L"strings are hard")
And so on.
Had ## occured in the NS_NAMED_LITERAL_STRING:
NS_NAMED_MULTILINE_LITERAL_STRING(n,L##s))
Then we would have LMY_STRING
