naming-conventions

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . What Delphi coding standards document(s) do you follow? Our company is looking at putting some better coding standards in place, to

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . What Delphi coding standards document(s) do you follow? Our company is looking at putting some better coding standards in place, to

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 4 years ago . What's the convention for naming functions in C++? I come from the Java environment so I usually name something like: myFunction(...) { } I've seen mixed code in C++, myFunction(....) MyFunction(....) Myfunction(....) What's the correct way? Also, is it the same for a class

问题 By convention classes are often named like nouns, methods like verbs and interfaces like adjectives. What is the common naming convention for a delegate? Or what's a good way to differentiate its name when delegates are listed among types and other things? My immediate assumption is to name a delegate more likely an adjective because a single method interface can often be replaced with a delegate. Some thoughts: delegate object ValueExtracting(object container); delegate object ValueExtractor

问题 I would like to know what special characters are allowed to be used in column name in T-SQL, MSSQL. So I know I can use letters and numbers, but are the other characters that are available without using brackets [] to refer to this column? 回答1: from MSDN: The first character must be one of the following: A letter as defined by the Unicode Standard 3.2. The Unicode definition of letters includes Latin characters from a through z, from A through Z, and also letter characters from other

问题 I am just learning Ruby and I don't quite understand the difference between several Ruby methods with and without a '!' at the end. What's the difference? Why would I use one over the other? 回答1: Methods with an exclamation mark at the end are often called bang-methods. A bang method doesn't necessarily modify its receiver as well as there is no guarantee that methods without a exclamation mark doesn't. It's all very well explained in this blog post. To quote the post: The ! in method names

问题 We have our own external convention of naming objects and I need to change the naming convention for the auto generated foreign key constraints. Now it looks like: FK_dbo.City_dbo.CityType_City_CityTypeId but I would like it to be called City_FKC_CityType . I found a similar question which says that you can change the name of constraints manually. However, this does not suit me, since I have a lot of tables and foreign key constraints. I found some information about "Custom Code First

问题 Often when I see class definitions class Foo: , I always see them start with upper case letters. However, isn't a list [] or a dict {} or some other built-in type, a class as well? For that matter, everything typed into the Python's IDLE which is a keyword that is automatically color coded in purple (with the Window's binary distribution), is itself a class, right? Such as spam = list() spam is now an instance of a list() So my question is, why does Python allow us to first of all do

问题 I come from a .NET world and I'm new to writting C++. I'm just wondering what are the preferred naming conventions when it comes to naming local variables and struct members. For example, the legacy code that I've inheritted has alot of these: struct MyStruct { TCHAR szMyChar[STRING_SIZE]; bool bMyBool; unsigned long ulMyLong; void* pMyPointer; MyObject** ppMyObjects; } Coming from a C# background I was shocked to see the variables with hungarian notation (I couldn't stop laughing at the pp

问题 What conventions are people here following for naming of instance variables and method arguments - particularly when method arguments are used to set ivars (instance variables)? In C++ I used to use the m_ prefix for ivars a lot. In C# I followed the convention of disambiguating purely by use of this. for ivars. I've since adopted the equivalent in C++ too ( this-> ). In Objective C I've tried a few things but none have really seemed satisfactory. Unless someone suggests something really nice