Just check the remainder of division by 10: if (day % 10 == 1) { result = “dan”; } else { result = “dana”; } % is the “Modulo” or “Modulus” Operator, unless you’re using JavaScript, in which case it is a simple remainder operator (not a true modulo). It divides the two numbers, and … Read more
Your problem stems from a misunderstanding of the or operator that is common to people learning programming languages like this. Yes, your immediate problem can be solved by writing x ~= 0 and x ~= 1, but I’ll go into a little more detail about why your attempted solution doesn’t work. When you read x … Read more
For generic SQL you can use CASE: CASE is used to provide if-then-else type of logic to SQL. Its syntax is: SELECT CASE (“column_name”) WHEN “condition1” THEN “result1” WHEN “condition2” THEN “result2” … [ELSE “resultN”] END FROM “table_name” From http://www.sqlite.org/lang_expr.html section “The CASE expression” E.g. UPDATE pages SET rkey = rkey + 2, lkey = … Read more
It really depends on what you’re trying to accomplish. If you have no else clause then if(!doSomething()) seems fine. However, if you have if(!doSomething()) { … } else { // do something else } I’d probably reverse that logic to remove the ! operator and make the if clause slightly more clear.
int first = stack.pop(); int second = stack.pop(); if (first == 1 && second == 1)
You are trying to micro-optimize here, and that’s generally a big no-no. Unless you have performance analytics which are showing you that this is an issue, it’s not even worth changing. For general use, the correct answer is whatever is easier to maintain. For the hell of it though, the IL for the null coalescing … Read more
They are pretty similar but each has a few special features. switch switch is usually more compact than lots of nested if else and therefore, more readable If you omit the break between two switch cases, you can fall through to the next case in many C-like languages. With if else you’d need a goto … Read more
if (Derived* derived = dynamic_cast<Derived*>(base)) { // do stuff with `derived` } Though this is oft cited as an anti-pattern (“use virtual dispatch!”), sometimes the Derived type has functionality that the Base simply does not (and, consequently, distinct functions), and this is a good way to switch on that semantic difference.
I use this kind of pattern often. It’s very compact: Define a constant in your class: private static final Set<Integer> VALUES = Set.of(12, 16, 19); // Pre Java 9 use: VALUES = new HashSet<Integer>(Arrays.asList(12, 16, 19)); In your method: if (VALUES.contains(x)) { … } Set.of() returns a HashSet, which performs very well even for very … Read more
1) Variables are visible for the whole function scope. Therefore, you should only declare them once. 2) You should not declare the variable twice in your example. I’d recommend declaring the variable at the top of the function, then just setting the value later: function actionPane(state) { var structure; if(state === “ed”) { structure = … Read more