naming

No doubt, it's essential for understanding code to give member variables a prefix so that they can easily be distinguished from "normal" variables. But what kind of prefix do you use? I have been working on projects where we used m_ as prefix, on other projects we used an underscore only (which I personally don't like, because an underscore only is not demonstrative enough). On another project we used a long prefix form, that also included the variable type. mul_ for example is the prefix of a m ember variable of type u nsigned l ong. Now let me know what kind of prefix you use (and please

What is the convention for suffixing method names with "Async"? Should the "Async" suffix be appended only to a method that is declared with the async modifier? public async Task<bool> ConnectAsync() Or is it enough that the method just returns Task<T> or Task ? public Task<bool> ConnectAsync() I think the truth is ambiguous even from Microsoft documentation: In Visual Studio 2012 and the .NET Framework 4.5, any method that is attributed with the async keyword ( Async in Visual Basic) is considered an asynchronous method, and the C# and Visual Basic compilers perform the necessary

I am trying to set Apache environment variables (for use in PHP) with the [E=VAR:VAL] flag on RewriteRule rules in an .htaccess file. I have already discovered the variables are accessed in PHP as server variables $_SERVER rather than $_ENV (which makes a certain amount of sense). However, my problem is for some rules the [E=VAR:VAL] flag works as expected and I end up with a variable $_SERVER['VAR'] but for other rules I end with a variable $_SERVER['REDIRECT_VAR'] or $_SERVER['REDIRECT_REDIRECT_VAR'] , etc A. What causes an environment variable set in Apache using the [E=VAR:VAL] flag to get

Which characters are illegal within a branch name? Manoj Govindan Naming rules for refname: Git imposes the following rules on how references are named: They can include slash / for hierarchical (directory) grouping, but no slash-separated component can begin with a dot . or end with the sequence .lock . They must contain at least one / . This enforces the presence of a category like heads/ , tags/ etc. but the actual names are not restricted. If the --allow-onelevel option is used, this rule is waived. They cannot have two consecutive dots .. anywhere. They cannot have ASCII control

Coming up with good, precise names for classes is notoriously difficult. Done right, it makes code more self-documenting and provides a vocabulary for reasoning about code at a higher level of abstraction. Classes which implement a particular design pattern might be given a name based on the well known pattern name (e.g. FooFactory, FooFacade), and classes which directly model domain concepts can take their names from the problem domain, but what about other classes? Is there anything like a programmer's thesaurus that I can turn to when I'm lacking inspiration, and want to avoid using generic

What is the purpose of naming your constraints (unique, primary key, foreign key)? Say I have a table which is using natural keys as a primary key: CREATE TABLE Order ( LoginName VARCHAR(50) NOT NULL, ProductName VARCHAR(50) NOT NULL, NumberOrdered INT NOT NULL, OrderDateTime DATETIME NOT NULL, PRIMARY KEY(LoginName, OrderDateTime) ); What benefits (if any) does naming my PK bring? Eg. Replace: PRIMARY KEY(LoginName, OrderDateTime) With: CONSTRAINT Order_PK PRIMARY KEY(LoginName, OrderDateTime) Sorry if my data model is not the best, I'm new to this! Here's some pretty basic reasons. (1) If a