greatbody
/
freeCodeCamp
mirror of https://github.com/freeCodeCamp/freeCodeCamp.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Edited some typos (#26118)

pull/26134/head^2
Hardik Sharma 2018-12-21 15:40:20 +05:30 committed by Manish Giri
parent e1e1f1cabb
commit ee930678cd
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
guide/english/cplusplus/clean-code-guidelines/index.md
View File

@ -34,15 +34,17 @@ int cucumber; // global variable "cucumber"
## Using goto, continue, etc.
This is a usual discussion among programmers, just like global variables, these types of statements are usually considered bad practice.
They are considered bad because they lead to ["spaghetti code"](https://en.wikipedia.org/wiki/Spaghetti_code). When we program we want a
linear flow, when using those statements the flow is modified and lead to a "twisted and tangled" flow.
Goto was used in the past when while, for, if functions, however, with the introduction of those structured programming was created.
In general avoid using goto unless you are sure it will make your code cleaner and easier to read. An example might be using it in nested loops.
The usage of break and continue are practically the same. Use them in switches and try to make functions with an only purpose so you only have one exit point.
The usage of break and continue are practically the same. Use them in switches and try to make functions with the only purpose so you only have one exit point.
![img](https://imgs.xkcd.com/comics/goto.png)