Option Explicit | use strict | and similar | non - sense
- Dominant language
- No language data
- Stars
- 4.8k
- Forks
- 6.1k
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 370
Description
The Option Explicit statement existence is a non-sense: Using it solve the problem of misspelled or non declared variables. Very Good.
Than why such behavior isn't implemented as the default in all programming languages and the need to type Option Explicit is removed completely from all languages that need something like it?
The same is valid for 'use strict'; in javascript and others:
Any good programming language must be designed bo allow good practice: so remove from it option explicit and use strict and make their behavior the default behavior without the need to declare them that is a stupid thing. Such a principle should be used everywhere: a good programming language doesn't have to allow negative programming practices as not declaring variables.
This principle (= good programming practice) must be promoted to become a standard implementation world-wide into all good programming languages so their default behaviors helps the user to prevent mistakes and bugs and strange working behaviors of the created applications.
---
#### Document Details
⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.*
* ID: 612c500c-a3ae-fefd-007f-926be9bd138f
* Version Independent ID: 0eb1270f-7027-8061-72d8-1ef2e1b3ffe9
* Content: [Option Explicit Statement - Visual Basic](https://learn.microsoft.com/en-us/dotnet/visual-basic/language-reference/statements/option-explicit-statement)
* Content Source: [docs/visual-basic/language-reference/statements/option-explicit-statement.md](https://github.com/dotnet/docs/blob/main/docs/visual-basic/language-reference/statements/option-explicit-statement.md)
* Product: **dotnet-visualbasic**
* GitHub Login: @KathleenDollard
* Microsoft Alias: **kdollard**
Contributor guide
Assessment
This issue has not been assessed yet.