naming-conventions

If I'm writing abstract data types in C, are the functions written to perform actions on these data types and exposed in the interface (.h files) called functions , methods , or something yet completely different? I can't seem to find a constructive answer anywhere. Is method a C++ specific term? Is method a C++ specific term? A "method" is an object-oriented programming term, and refers to a function that is part of the namespace of an object. So you can create methods for objects in languages like C++, Java, Objective-C, etc. In C on the otherhand, you still have stand-alone functions, not

Does a class name, say UIImage+Something or UIImageView+Somethingelse , mean that it acts like a custom UIImage or UIImageView ? I think you are looking at the file names of Categories, not Classes. The plus character + is not allowed in class names or any other identifier in Objective-C. An Objective-C category is a way of adding methods (but not instance variables) to a class you don't necessarily have the source to. For example, if you frequently want to make upside-down copies of UIImages, you can use a category to add a upsideDownImage method onto the UIImage class. It's common to save

Section 10.2 of Java conventions recommends using class names instead of objects to use static variables or methods, i.e. MyClass.variable1 or MyClass.methodName1() instead of MyClass Obj1 = new MyClass(); Obj1.variable1; Obj1.methodName1(); There is no explanation of the rationale behind this, although I suspect this has something to do with memory use. It would be great if someone could explain this. I guess you mean "for static methods and variables". There is no difference regarding memory, except of course if you create the instance just for calling the method. Conventions aren't for

I'm designing a namespace to hold a set of classes that will handle user related tasks for a several different applications. (Log-in, authenticate etc) The problem is the namespace will be called Fusion.User but then it requires a class in that namespace that makes sense to call User . Should you have a class with the same name as the namespace? Or am I taking the wrong approach here? Having class named in the same way as the name space (package) may lead to a thought that class is central to the package. But if I get it correctly User is just a data object in your case. As far as I see you

I was looking at google go's runtime source code (at https://go.googlecode.com/hg/src/pkg/runtime/ ), and it seems they use a special character for their function names, · . (Look for example at https://go.googlecode.com/hg/src/pkg/runtime/cgocall.c ). Is this accepted across major compilers? It's not ANSI C, is it? Or is it just some macro magic? Thank you! C90 doesn't allow additional character in identifier (over those in the basic characters set), C99 do (both with the universal character syntax -- \uXXXX and \UXXXXXXXX -- and an implementation defined set of other characters). 6.4.2.1/1

I understand T comes from Type , but why is it that the next variable often used is K ? I've seen K used for Key but not frequently as the "next" type parameter. For example, you'll see Dictionary<K, V> where K is for Key and V is for Value . Sometimes you'll see T1 , T2 , etc. or T , U , V (the former is preferred here). But I prefer more descriptive names like Map<TSource, TDestination> or Create<TUnitOfWork> My guess would be that it's from Key . One more variation is the GenericFunction<T1,T2,TResult> , where TResult is the type of value returned by the functon. (as in, Func<T1,T2,...

Which naming convention do you use for local constants in C# and why? const int Pi = 3; const int pi = 3; It seems the trade-off is between lower camel-case indicating restricted scope, and upper camel-case being more readable and easier to move to a class level. I've noticed StyleCop prefers upper camel-case. I'm used to upper case (pascal case) for everything except variables and fields. Global constants are an exception to the fields, I don't know why, probably because they are public in some cases. Local constants are also lowercase so. It's just a matter of taste imo. Of course, within a