I would say that first and foremost: be consistent. I reckon you are almost there with the conventions that you have outlined in your question. A couple of comments though: Points 1 and 2 are good I reckon. Point 3 – sadly this is not always possible. Think about how you would cope with a … Read more
Microsoft recommends using singular for Enums unless the Enum represents bit fields (use the FlagsAttribute as well). See Enumeration Type Naming Conventions (a subset of Microsoft’s Naming Guidelines). To respond to your clarification, I see nothing wrong with either of the following: or
_ has 3 main conventional uses in Python: To hold the result of the last executed expression in an interactive interpreter session (see docs). This precedent was set by the standard CPython interpreter, and other interpreters have followed suit For translation lookup in i18n (see the gettext documentation for example), as in code like raise … Read more
Enums are classes and should follow the conventions for classes. Instances of an enum are constants and should follow the conventions for constants. So There is no reason for writing FruitEnum any more than FruitClass. You are just wasting four (or five) characters that add no information. This approach is recommended by and used in … Read more
The Unity convention is actually rather simple: everything is Pascal-cased, types (classes, structs, enums) and methods start with upper-case, fields and properties with lower-case. Enum values in upper-case, constants in lower-case (usually). So ClassName, MethodName, myField, myProperty { get; set; }, MyEnum.CaseA… that’s it. As for your example, Transform is a class, whereas transform is an accessor to the instance of Transform in that particular GameObject/Component. … Read more
The following answer is largely sourced from this answer. If you’re going to follow PEP 8, you should stick to all-lowercase names, with optional underscores. To quote PEP 8’s naming conventions for packages & modules: Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. And for classes: Class … Read more
File extensions do not have any bearing or impact on the content of the file. You can hold YAML content in files with any extension: .yml, .yaml or indeed anything else. The (rather sparse) YAML FAQ recommends that you use .yaml in preference to .yml, but for historic reasons many Windows programmers are still scared of using extensions with more than three characters … Read more
Single Underscore Names, in a class, with a leading underscore are simply to indicate to other programmers that the attribute or method is intended to be private. However, nothing special is done with the name itself. To quote PEP-8: _single_leading_underscore: weak “internal use” indicator. E.g. from M import * does not import objects whose name starts with an … Read more
A ‘$’ in a variable means nothing special to the interpreter, much like an underscore. From what I’ve seen, many people using jQuery (which is what your example code looks like to me) tend to prefix variables that contain a jQuery object with a $ so that they are easily identified and not mixed up with, say, … Read more
In English, a “collection of stamps” is a “stamp collection”. (At best, “stamps collection” would be understood). In programming, I’m not entirely sure why, but we1 do sometimes use the form “StampsCollection”. It may be because we try to use more precise and logical lingo than traditional English provides; we start with the name “Item”, pluralise it to “Items”, then be precise … Read more