FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Fix: Corrected terminologies for break and continue. They shouldn't be called directive by Shivamaggw · Pull Request #3985 · javascript-tutorial/en.javascript.info · GitHub

Fix: Corrected terminologies for break and continue. They shouldn't be called directive - #3985

Open
Shivamaggw wants to merge 1 commit into
javascript-tutorial:masterfrom
Shivamaggw:patch-2
Open

Fix: Corrected terminologies for break and continue. They shouldn't be called directive#3985
Shivamaggw wants to merge 1 commit into
javascript-tutorial:masterfrom
Shivamaggw:patch-2

Conversation

Copy link
Copy Markdown

In JavaScript, break and continue are technically called statements, not directives or operators. Here is why they do not fit the other categories:

Why they are Statements

  • They perform actions: A statement is a piece of code that instructs the computer to do something (like controlling the loop flow) rather than producing a value.
  • Official Spec: The ECMAScript (JavaScript) specification officially categorizes them as "Iteration Statements" or "Control Flow Statements."

Why they are NOT Operators

  • Operators produce values: Operators (like +, ===, or &&) take operands, perform an action, and return a result.
  • break and continue return nothing: You cannot assign them to a variable (e.g., let x = break; is a syntax error).

Why they are NOT Directives

  • Directives change environment behavior: In JavaScript, a directive is a literal expression that tells the browser engine to change how it parses code (for example, "use strict";).
  • They do not control loops: Directives apply to entire scripts or functions, not block-level loop iterations.

…e called directive

In JavaScript, break and continue are technically called statements, not directives or operators.
Here is why they do not fit the other categories:
## Why they are Statements

* They perform actions: A statement is a piece of code that instructs the computer to do something (like controlling the loop flow) rather than producing a value.
* Official Spec: The ECMAScript (JavaScript) specification officially categorizes them as "Iteration Statements" or "Control Flow Statements."

## Why they are NOT Operators

* Operators produce values: Operators (like +, ===, or &&) take operands, perform an action, and return a result.
* break and continue return nothing: You cannot assign them to a variable (e.g., let x = break; is a syntax error).

## Why they are NOT Directives

* Directives change environment behavior: In JavaScript, a directive is a literal expression that tells the browser engine to change how it parses code (for example, "use strict";).
* They do not control loops: Directives apply to entire scripts or functions, not block-level loop iterations.
javascript-translate-bot added the review needed Review needed, please approve or request changes label Aug 2, 2026
javascript-translate-bot requested review from a team August 2, 2026 19:51

Copy link
Copy Markdown


Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review needed Review needed, please approve or request changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants


Back | FazBrowse Home | New Git URL