Timeline for Is there any value in teaching goto statement or flowcharts?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 28, 2017 at 10:11 | comment | added | Ben I.♦ | @Manngo switch would involve conditional jumps, not particularly unconditional ones (unless you are referring to the default at the end?) But in any case, there is a philosophical dissimilarity here. By that measure, so do if statements. The purpose isn't to find every jump that a compiler would generate, but rather, to find the ones that pull a program out of the narrative flow of the program (which is the use-case that so readily creates spaghetti code) | |
| Sep 28, 2017 at 10:10 | history | edited | Ben I.♦ | CC BY-SA 3.0 | Fixed errors thanks to comments by Paŭlo Ebermann, Peter A. Schneider, and Manngo |
| Sep 28, 2017 at 8:57 | comment | added | Manngo | And a fifth one: switch | |
| Sep 28, 2017 at 1:51 | comment | added | Ben I.♦ | @PeterA.Schneider 6502 is useful for me because it is what they have studied, so it's a good point of reference. It's also a beautifully clean and simple assembly language | |
| Sep 27, 2017 at 22:33 | comment | added | Peter - Reinstate Monica | Also note that the Java virtual machine bytecode has unconditional jumps (of course). It could be instructive to show the bytecode for loops and conditional expressions (instead of comparing unrelated 6502 assembler). | |
| Sep 27, 2017 at 22:25 | comment | added | Peter - Reinstate Monica | @PaŭloEbermann And System.exit(). | |
| Sep 27, 2017 at 21:10 | comment | added | Paŭlo Ebermann | There is a fourth one: throw. | |
| Sep 27, 2017 at 19:21 | history | answered | Ben I.♦ | CC BY-SA 3.0 |