It is considered acceptable practice to isolate these decisions in a function and use returns instead of breaks. While all these checks correspond to the same level of abstraction as of the function, it is quite logical approach. For example: void foo(…) { if (!condition) { return; } … if (!other condition) { return; } … Read more
First choice: Associative array This requires bash 4.0 or newer to support declare -A; see below for other options. #!/bin/bash # first, read your key/value pairs into shell variables declare -A v=( ) while read -r var value; do v[$var]=$value done < Parameters.conf # second, perform a command that depends on them sqlplus / as … Read more
I am not sure about DO-WHILE IN MS SQL Server 2008 but you can change your WHILE loop logic, so as to USE like DO-WHILE loop. Examples are taken from here: http://blog.sqlauthority.com/2007/10/24/sql-server-simple-example-of-while-loop-with-continue-and-break-keywords/ Example of WHILE Loop DECLARE @intFlag INT SET @intFlag = 1 WHILE (@intFlag <=5) BEGIN PRINT @intFlag SET @intFlag = @intFlag + 1 … Read more
Two simple solutions: Execute your code once before the while loop actions() { check_if_file_present # Do other stuff } actions #1st execution while [ current_time <= $cutoff ]; do actions # Loop execution done Or: while : ; do actions [[ current_time <= $cutoff ]] || break done
I always follow the rule that if it should run zero or more times, test at the beginning, if it must run once or more, test at the end. I do not see any logical reason to use the code you listed in your example. It only adds complexity.
I wouldn’t say it’s bad – but equally I would normally at least look for an alternative. In situations where it’s the first thing I write, I almost always at least try to refactor it into something clearer. Sometimes it can’t be helped (or the alternative is to have a bool variable which does nothing … Read more
If you always want the loop to execute at least once. It’s not common, but I do use it from time to time. One case where you might want to use it is trying to access a resource that could require a retry, e.g. do { try to access resource… put up message box with … Read more
I am not sure what you are trying to do. You can implement a do-while loop like this: while True: stuff() if fail_condition: break Or: stuff() while not fail_condition: stuff() What are you doing trying to use a do while loop to print the stuff in the list? Why not just use: for i in … Read more
change while ((action != 1) || (action != 2) || (action != 3) || (action != 4)); // (1) to while ((action != 1) && (action != 2) && (action != 3) && (action != 4)); // (2) Analysis: if action == 1 (1) will evaluate to while(false || true || true || true) => … Read more
Take the System.out out of the loop int w=-10; System.out.println(w); do { w++; } while (w<=2020); System.out.println(w-1);