naming-conventions

问题 I'm a new developer I have never worked in big enterprise company so I have a question about naming conventions in multi-layer application. I have a WPF/MVVM application, with EF data layer. I also want to adjust DDD principles. So, I three models of the same class I would say. I have "model" in MVVM, I have a entity/dto(I don't know?) in EF, I have domain model/POCO in DDD. I have to create all those 3 classes to separate concerns (maybe I could merge MVVM model with POCO. I mean, POCO is

问题 This is somewhat a follow-up to Repeating module name for each module component question. We've decided to follow the suggested in Best Practice Recommendations for Angular App Structure blog post angular project organization and naming conventions while building a small internal application for measuring connection quality. And this is what we've got at the moment: $ tree -L 1 . ├── app-config-service.js ├── app-config-service_test.js ├── app-connection-service.js ├── app-connection-service

问题 According to Apple's naming convention for high resolution images When we provide just name.png, iphone 3 and iphone 4 will display it. When we provide also name@2x.png which has higher resolution than name.png, this time iphone3 will display name.png and iphone 4 will display name@2x.png. Here is my question what if we only provide name@2x.png? Ok, iphone 4 will display it. Can iphone 3 display this image? Thank you in advance.. 回答1: No, it can't. Non-retina devices will not find the image

问题 This question already has answers here : Closed 7 years ago . Possible Duplicate: Why are dashes preferred for CSS selectors / HTML attributes? Personally I use "lower-case with dashes" to format my HTML classes, which seems to be the standard these days. Using something like camel case seems more reserved for JavaScript in my eyes, but I realise that's just my opinion. I'm trying to improve front-end code consistency at my workplace and part of that will be coding guidelines. Rather than

问题 I am quite confused by looking at the boost library, and stl, and then looking at people's examples. It seems that capitalized type names are interspersed with all lowercase, separated by underscores. What exactly is the way things should be done these days? I know the .NET world has their own set of conventions, but it appears to be completely different than the C++ sphere. 回答1: What a can of worms you've opened. The C++ standard library uses underscore_notation for everything, because that

问题 If I am naming a new class in an OOP language, which is a better convention: XMLWriter Most common XMLwriter Easier to distinguish XmlWriter No longer an acronym XML_Writer Removes the point of camel case Pedantic yes, but I'm curious who uses what and why. 回答1: Java conventions seem lately to favor treating well-known acronyms like words, so: "XmlWriter"... http://www.ibm.com/developerworks/library/ws-tip-namingconv.html Java Naming Convention with Acronyms <-dupe question? http://geosoft.no

问题 I was looking clojure.core 's macro implementation of and and I noticed that some of the let bindings in this source file's macros end their variable name with and octothorpe ( # ). Upon further inspection with the following code... (defn foo# [] 42) (foo#) ; => 42 ...I realized that octothorpe is just a valid symbol (at least when included on the end). So, my question is, why do these core macros end their binding symbols with a hash character? Is there some specific implied meaning or

问题 Assume that I have a class that exposes the following event: public event EventHandler Closing How should methods that are registered to this event be named? Do you prefer to follow the convention that Visual Studio uses when it assigns names to the methods it generates (aka. +=, Tab, Tab)? For example: private void TheClass_Closing( object sender, EventArgs e ) Or do you use your own style to name these methods? I've tried different ways to name these methods (like TheClassClosing ,

问题 I've always wondered if there are any naming convetions as when to use ALLCAPS for a type and when to append _t (and when to not use anything?). I know back in the days K&R published all kinds of documents about how to use C, but I couldn't find anything about this. Among the C standard library types, _t seem prettys dominant time_t clock_t uint32_t size_t sig_atomic_t ... , as opposed to FILE , va_list or struct tm . Are there actually rules to this or is it completely arbitrary? Microsoft

问题 I'm looking for a good name to give to data structures that are thread safe / internally synchronized. The C++ standard uses the term atomic , but atomic has some rather special meaning. Microsoft uses the term Concurrent in their Thread-Safe Collections (or in C++ _concurrent in the Parallel Containers). What I really would like would be a generic wrapper for (value) types that provides a similar set of operations to what std::atomics do, but with a different name, and some typedefs derived