naming-conventions

问题 I've come across the following code snippet (a function definition): choose (x:xs) = choosep x xs where choosep x [] = x choosep x (_:_) = x choosep _ (x:xs) = choosep x xs in Curry programming language in a "standard library"--/usr/lib/curry-0.9.11/Success.curry from Muenster Curry Compiler. Here: choose :: [a] -> a and choosep :: a -> [a] -> a -- BTW, not a _p_redicate Is the "p" suffix for the helper recursive function choosep a known naming convention? Perhaps it comes from functional

问题 What are the naming conventions for packages with names that contain more than one word? Lets say I have a package named 'garden hose', should I name it garden_hose, gardenHose or simply gardenhose? I know that packages are normally named with lower-case letters only. I only see package names made out of one word in the api, are there any conventions for package names made out of several words? With classes we have: ClassName. For instance RaceCar, what about packages? I have a package named

问题 How can I resolve logical entity names to full class names in Symfony2? Like MyAcmeBundle:User to My\AcmeBundle\Entity\User . 回答1: You can get the ClassMetadata from the EntityManager which will resolve the namespace into a fully qualified class name. <?php echo $manager->getClassMetadata('MyAcmeBundle:User')->getName(); 来源： https://stackoverflow.com/questions/11406697/how-can-i-resolve-myacmebundleuser-to-my-acmebundle-entity-user-in-symfony2

问题 Anyone have a naming strategy that works well for service proxy classes? For example, if I am given three web services within two projects as follows: XWs AService.asmx YWs BService.svc CService.svc What would use as the Service Reference Name & Namespace for AService , BService and CService ? In general, I'd like something in the proxy name/namespace to indicate that the thing being used is not a concrete class, but represents a proxy - both so it doesnt clash with usage of concrete classes

问题 I have a question about using PrimaryKeyNamingConvention Suppose the following class: public class banco { [Required] public virtual int banco_id { get; set; } ... } and public class PrimaryKeyNamingConvention : IIdConvention { public void Apply(IIdentityInstance instance) { instance.Column(instance.EntityType.Name + "_id"); } } and static AutoPersistenceModel CreateAutomappings() { ... Conventions.Setup(c => { c.Add<PrimaryKeyNamingConvention>(); }); You can use something like described

问题 In a discussion with a peer, it was brought up that we should consider using auto properties for all class level variables... including private ones. So in addition to a public property like so: public int MyProperty1 { get; set; } Our private class-level variables would look like this: private int MyProperty2 { get; set; } Instead of: private int _myProperty2; I'm on the fence about why someone would want to do this but I can't decide if my reluctance to accept this is because of my own

问题 How do you name repository and service interfaces and their implementing classes? For example I have a model with the name Question . What would you name the repository (interface and implementation) and the service (interface/implementation). After reading these posts: Java Interfaces/Implementation naming convention and Interface naming in Java I reconsidered what I already had done :) 回答1: I think that there are roughly two approaches to naming in DDD: 1) Stereotype based. This is where

问题 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 7 years ago . I'm wondering what the best practice is for naming primary/unique keys in a database with many tables. Should you always just call

问题 I understand that in MVC pattern and in REST services it is common to use URIs like /items/{id} but what is bad thing about using query parameters in the URI? GET /items/{id} vs GET /items?id={id} Further, lets say an entity has 'referenceId' field that points to some related (say parent) entity, and I need to create REST service to get all items for parent entity, which way is better: GET(POST) /items/parent/{parentId} or GET(POST) /items?parent={parentId} Will be grateful for insights that

问题 When I read code that uses Select I think "select-all-where". When I read code that uses Map I think "this-to-that" or "apply-to-all". I can't be the only person that feels the name Select is confusing. Map 回答1: It's really identical to map from functional languages. The reason it's named Select is that it's designed to be used as a part of LINQ which uses SQL-like keywords. from item in collection where item.Value == someValue select item.Name is translated to: collection.Where(item => item