naming-conventions | 易学教程

F# naming convention

阅读更多关于 F# naming convention

Is there an "official" naming / casing convention for F#? I'm always in doubt of using C# style or not: Class.MyFunctionName or Module.my_function_name In F# you're meant to mix BCL classes and F# library ones: they have different casing and the code looks very ugly. Yes, there is confusion, because F# has morphed from OCaml to .Net over the years. Basically, the naming conventions are a "breaking change" - old code is inconsistent with new code. However, the May 2009 CTP has settled the issue. The Release Notes say... Standard Library Naming Conventions The naming conventions adopted for the

Fluent NHibernate primary key constraint naming conventions

阅读更多关于 Fluent NHibernate primary key constraint naming conventions

Is there any way to create a naming convention for my primary key constraints in Fluent NHibernate? I know you can name foreign key constraints, but it does not appear possible to name the primary key constraint. James Gregory from FNH says... No, that's not supported through NHibernate, so we can't support it either. http://groups.google.com/group/fluent-nhibernate/browse_thread/thread/9ea7155407d33772 来源： https://stackoverflow.com/questions/1358043/fluent-nhibernate-primary-key-constraint-naming-conventions

Naming conventions for Code First migrations

阅读更多关于 Naming conventions for Code First migrations

问题 We are using code first migrations to keep our database and model in sync. At the moment we have the version number as name for the migration which clearly doesn't work out. The problem is that multiple migrations with the same name where created by different developers independent of each other for their local database. This led to some weird behavior as the IMigrationMetadata.Id was different because of the time stamp but the classes are partial with the same name. What is the way to go to

Programmers dictionary/lexicon for non native speakers

阅读更多关于 Programmers dictionary/lexicon for non native speakers

问题 I'm not an English speaker, and I'm not very good at English. I'm self thought. I have not worked together with others on a common codebase. I don't have any friends who program. I don't work with other programmers (at least nobody who cares about these things). I guess this might explain some of my problems in finding good unambiguous class names. I have tried to find some sort of "Programmers dictionary" containing words often used and their meanings. When reading others code I have to look

Naming conventions for controls

阅读更多关于 Naming conventions for controls

While working with VS by default the editor generates this: <asp:Button ID="Button1" runat="server" Text="Button" /> Now the ID generated is Button1 i.e First letter capital. My questions is what is the best way to name the controls ? SubmitButton btnSubmit or something else? Which naming convention is considered good ? btnSubmit is Hungarian notation which I don't personally consider good for UI programming since the type of control is evident directly through its declaration or intellisense in Visual Studio. SubmitButton is better. Generally it takes a form - Purpose-TypeOfControl For

Standard naming to the Spring beans

阅读更多关于 Standard naming to the Spring beans

问题 Somebody knows an standard naming to the Spring beans in a App Context? I used the camel case naming, but I'm not sure if exists an kind of standard, I searched in the net about that but I haven't found something. 回答1: Bean Naming Conventions (Spring Manual section 3.3.1) The convention is to use the standard Java convention for instance field names when naming beans. That is, bean names start with a lowercase letter, and are camel-cased from then on. Examples of such names would be (without

Naming convention for const object keys in ES6

阅读更多关于 Naming convention for const object keys in ES6

问题 Is there a recommended naming convention for key names within a const object in es6? I haven't been able to find a resource which states if they should be uppercase or lowercase. const COLOR_CODES = { BLUE: 1, RED: 1 }; vs const COLOR_CODES = { blue: 1, red: 1 }; The examples from this MDN article show both styles, so maybe both are acceptable. 回答1: According to Google it would be all caps. Speaking from experience, most of the other programming languages have all caps so I would suggest

What are the Laravel naming conventions for controllers/models/views?

阅读更多关于 What are the Laravel naming conventions for controllers/models/views?

问题 I remember hearing you should name your controllers, models and views in a special way. Either singular or plural. I don't remember which ones to name what though, and i can't find anything about it in the doc. I'm guessing it's like this: Controllers are plural Views are plural Models are singular Am i on the right track? I understand it's just a convention and you don't have to follow them, but i still want to know what the right way is. 回答1: In ASP.NET MVC, I use the convention you

Why does Ruby use respond_to? instead of responds_to?

阅读更多关于 Why does Ruby use respond_to? instead of responds_to?

问题 I'm curious why Ruby's introspection related method to check if an object responds to a method is respond_to? instead of responds_to? It always seems awkward to me but maybe that's because I'm used to respondsToSelector in objective-c. 回答1: Matz prefers second person singular or third person plural: "responds_to?" probably makes more sense to English speakers than "respond_to?". Maybe. But I'm Japanese. Ruby is not English. It's the basic naming rule to avoid third person singular form in the

Am I immoral for using a variable name that differs from its type only by case?

阅读更多关于 Am I immoral for using a variable name that differs from its type only by case?

问题 For instance, take this piece of code: var person = new Person(); or for you Pythonistas: person = Person() I'm told constantly how bad this is, but have yet to see an example of the immorality of these two lines of code. To me, person is a Person and trying to give it another name is a waste of time. I suppose in the days before syntax highlighting, this would have been a big deal. But these days, it's pretty easy to tell a type name apart from a variable name. Heck, it's even easy to see