goto

hello i got a batch file, something like this: if %day%==monday, tuesday, wednesday, thursday, friday ( goto yes ) else ( goto no ) Now i know the first line won't work. What i actually want to happen: It automatticly checks which day it is. If it is Monday to Friday, it has to go to 'yes', otherwise (saturday/sunday) to 'no'. How to do this? I ran across this online. Tested, and it works. Returns the day as an integer, which you can still work with. @For /F "tokens=2,3,4 delims=/ " %%A in ('Date /t') do @( Set Month=%%A Set Day=%%B Set Year=%%C ) @echo DAY = %Day% @echo Month = %Month% @echo

Should developers avoid using continue in C# or its equivalent in other languages to force the next iteration of a loop? Would arguments for or against overlap with arguments about Goto ? I think there should be more use of continue! Too often I come across code like: for (...) { if (!cond1) { if (!cond2) { ... highly indented lines ... } } } instead of for (...) { if (cond1 || cond2) { continue; } ... } Use it to make the code more readable! Is continue any more harmful than, say, break ? If anything, in the majority of cases where I encounter/use it, I find it makes code clearer and less

I've heard that it's been proven theoretically possible to express any control flow in a Turing-complete language using only structured programming constructs, (conditionals, loops and loop-breaks, and subroutine calls,) without any arbitrary GOTO statements. Is there any way to use that theory to automate refactoring of code that contains GOTO s into code that does not? Let's say I have an arbitrary single subroutine in a simple imperative language, such as C or Pascal. I also have a parser that can verify that this subroutine is valid, and produce an Abstract Syntax Tree from it. But the

What if I have nested loops, and I want to break out of all of them at once? while (true) { // ... while (shouldCont) { // ... while (shouldGo) { // ... if (timeToStop) { break; // Break out of everything? } } } } In PHP, break takes an argument for the number of loops to break out of. Can something like this be done in C#? What about something hideous, like goto ? // In the innermost loop goto BREAK // ... BREAK: break; break; break; Extract your nested loops into a function and then you can use return to get out of the loop from anywhere, rather than break. Introduce another control flag and

Google's Go language is a new language. Therefor I was surprised to find that it has a 'goto' statement. I've always been taught that 'goto' statements are a thing of the past and evil for it occludes the actual flow of a program. Function (or methods if you will) are always a better way of controlling flow. I must be missing something. Why and when is using 'goto' a good idea? Or why did Google include it? Kissaki When we actually check Gos source code ( the standard library ), we can see where goto s are actually well applied. For example, in the math/gamma.go file, the goto statement is