About the variables names, library implementors must use “crazy” naming conventions, such as names starting with an underscore followed by an uppercase letter, because such names are reserved for them. They cannot use “normal” names, because those may have been redefined by a user macro. Section 17.6.3.3.2 “Global names” ยง1 states: Certain sets of names … Read more
There is a discrepancy between the two examples. The first will execute the “do something” at least once every time even if the statement is never true. The second will only “do something” when the statement evaluates to true. I think what you are looking for is a do-while loop. I 100% agree that while … Read more
Don’t put anything between the strings. Part of the C++ lexing stage is to combine adjacent string literals (even over newlines and comments) into a single literal. #include <iostream> #include <string> main() { std::string my_val =”Hello world, this is an overly long string to have” ” on just one line”; std::cout << “My Val is … Read more
If you need an algorithm, try this: Convert the color from RGB space to HSV space (Hue, Saturation, Value). If your UI framework can’t do it, check this article: http://en.wikipedia.org/wiki/HSL_and_HSV#Conversion_from_RGB_to_HSL_or_HSV Hue is in [0,360). To find the “opposite” color (think colorwheel), just add 180 degrees: h = (h + 180) % 360; For saturation and … Read more
You missed one. First code for correctness, then for clarity (the two are often connected, of course!). Finally, and only if you have real empirical evidence that you actually need to, you can look at optimizing. Premature optimization really is evil. Optimization almost always costs you time, clarity, maintainability. You’d better be sure you’re buying … Read more
Exceptions are not conditionals. The conditional version is clearer. That’s natural: this is straightforward flow control, which is what conditionals are designed for, not exceptions. The exception version is primarily used as an optimization when doing these lookups in a loop: for some algorithms it allows eliminating tests from inner loops. It doesn’t have that … Read more
The first is more idiomatic. In particular, it indicates (in a 0-based sense) the number of iterations. When using something 1-based (e.g. JDBC, IIRC) I might be tempted to use <=. So: for (int i=0; i < count; i++) // For 0-based APIs for (int i=1; i <= count; i++) // For 1-based APIs I … Read more
I agree with you – to me, uppercase is just SHOUTING. I let my IDE handle making keywords stand out, via syntax highlighting. I don’t know of a historical reason for it, but by now it’s just a subjective preference. Edit to further make clear my reasoning: Would you uppercase your keywords in any other … Read more
public boolean userExists(…) Would be my prefered. As it makes your conditional checks far more like natural english: if userExists … But I guess there is no hard and fast rule – just be consistent
Extending @KooiInc answer, you can avoid manually escaping every special character by using the source property of the RegExp object. Example: var urlRegex= new RegExp(” + /(?:(?:(https?|ftp):)?\/\/)/.source // protocol + /(?:([^:\n\r]+):([^@\n\r]+)@)?/.source // user:pass + /(?:(?:www\.)?([^\/\n\r]+))/.source // domain + /(\/[^?\n\r]+)?/.source // request + /(\?[^#\n\r]*)?/.source // query + /(#?[^\n\r]*)?/.source // anchor ); or if you want to … Read more