Objective-C is a strict super set of C. That is to say, absolutely anything that will work in C will also work exactly as is in Objective-C. What's more, Objective-C projects can even seamlessly integrate pure C files. This isn't necessarily all that common, but what is very common is significant chunks of pure C code in the middle of an Objective-C file.
I present this question as an example: Creating a better NSLog
Would a C language tag be appropriate/acceptable here?
When you have an objective-c question in front of you and are considering adding a c tag on it, ask yourself this question:
Would someone who knows c but not objective-c be interested in reviewing this code, as if it was c?
Regarding your specific example question there, I think the answer is no. I say this mainly because of lines like these:
timeStampFormat = [[NSDateFormatter alloc] init];
[timeStampFormat setDateFormat:@"yyyy-MM-dd HH:mm:ss.SSS"];
[timeStampFormat setTimeZone:[NSTimeZone systemTimeZone]];
That doesn't look like C at all to me.
@import thing too...?
\$\endgroup\$
If you intend for the code to be polyglot, then use both tags. Otherwise, if you only want it to work as Objective-C, then just the objective-c tag should be used.
