Variable Names Beginning With Underscore Is Not Encouraged. Why


Answer ( 1 )


    Variable Names Beginning With Underscore Is Not Encouraged. Why

    When you’re developing a software application or website, it makes sense to use variables that are descriptive and easy to remember. However, Variable names that begin with an underscore (e.g., _underscore) is not recommended in most languages. Why? Well, this variable name is reserved for system variables in most programming languages. And while the underscore may seem like a harmless character, it can cause problems when displayed in different contexts. For example, when a user tries to input the underscore into a text field on your website or application, they may get an error message. As you can see, there are plenty of reasons why you might want to avoid using variable names that begin with an underscore. If you’re not sure whether your variable name falls into this category or not, be sure to check with your development team or language documentation.

    What is the Problem with Variable Names Beginning With Underscore?

    There is a problem with variable names that begin with an underscore. When you create a new variable in code, JavaScript will give it the name _first_name_last_name_. This can make your variables difficult to read and debug. It’s best to avoid starting variable names with an underscore.

    What are Some Examples of Variable Names That Are Not Recommended?

    Variable names that begin with an underscore are discouraged in JavaScript because they can cause confusion. For example, _foo is not the same as foo. This ambiguity can lead to errors or unexpected behaviour. Some other examples of variable names that are not recommended include _bar and __baz.

    How Can You Avoid Having Your Variable Name Begin with an Underscore?

    When naming variables in your code, it’s important to avoid having them start with an underscore. This is because the convention for variable names in most programming languages is to use lowercase letters. Starting a variable name with an underscore will usually cause errors when you try to use that variable in your code.

    There are a few reasons why you might want to use an underscore in a variable name. Sometimes, it can make the name more memorable. For example, if you were developing a function that used several of these variables, using an underscore in the variable name would help you remember which one was which.

    However, there are other times when starting a variable name with an underscore is not recommended. One reason is that it can cause issues when you try to reference that variable later in your code. If the name starts with an underscore, Visual Studio will typically generate an error when you try to access the value of the variable.

    Overall, it’s generally best to avoid using variables that begin with an underscore in your code. Unless there are specific reasons why you need to do so, it’s best to stick to lowercase letters for variable names.


    As developers, we all want our code to be as DRY and readable as possible. But does that mean we have to be against using underscores in variable names? Not at all! In fact, there are plenty of good reasons why you might choose to use underscores in your variable names. In this article, I’ll outline four good reasons why you might want to use underscores in a variable name: they’re easy to understand and remember, they make the code more organized and concise, they help avoid name clashes with other variables, and finally, they can help indicate special significance or importance to the variable. So if you’re considering using underscores in your next project, think carefully about whether or not it’s the right decision for your codebase – but don’t let the fear of potential naming collisions stop you from trying it out!

Leave an answer