Chris Waterson wrote: > Is it safe to do: > > #define MY_STRING "strings are hard" > NS_NAMED_LITERAL_STRING(kMyString, MY_STRING); > > I ask because it looks like this might eventually end up doing: > > LMY_STRING > > Is the order of macro expansion well-defined? Does use of the ## > operator in NS_L() make it not matter? 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). > Also, it appears that it is currently not possible to use a ``named > literal string'' as a static class member. Ought we support that? scc? jag
