GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |
GeezerVison is showing github.com — Fix: Corrected terminologies for break and continue. They shouldn't be called directive by Shivamaggw · Pull Request #3985 · javascript-tutorial/en.javascript.info ConversationIn 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
Why they are NOT Operators
Why they are NOT Directives
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions…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.
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ReviewersNo reviewsUh oh!
There was an error while loading. Please reload this page. AssigneesNo one assignedLabels
review needed
ProjectsMilestoneNo milestoneDevelopmentSuccessfully merging this pull request may close these issues. Uh oh!
There was an error while loading. Please reload this page. Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later. | |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |