Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When I create a protocol, I was used to put it right into the .h from a class that this protocol belongs to. But what when I want a pretty “general” protocol that a lot of classes might use? Would I make a .h file for this protocol only? And if so, are there special naming conventions to distinguish it from a class header file?
I think whatever is the clearest, most obvious way of doing it is the “right” way. In the case you describe having the protocol in its own header file probably does make sense.
There’s no generally accepted naming convention for protocols so, again, call it something that makes sense.