Does Underscore Prefix in JavaScript Truly Enforce Private Members?

Underscore Prefix: Convention or Significance in JavaScript

In programming, the underscore prefix is commonly used to denote private or internal elements. Is this convention merely a suggestion in JavaScript, akin to the treatment of private methods in Python?

Python's documentation states that variables prefixed with underscores are intended to remain as non-public members of a class. Does JavaScript follow this paradigm?

In JavaScript, the underscore prefix holds no inherent meaning within the language syntax. It is solely a convention employed by developers to indicate that a property or method is not intended for external use.

Consider the following code snippet:

<code class="javascript">function AltTabPopup() {
    this._init();
}

AltTabPopup.prototype = {
    _init : function() {
        ...
    }
}</code>

Here, _init is designated as an internal method by the underscore prefix. Similarly, private variables can be marked with underscores as well:

<code class="javascript">this._currentApp = 0;
this._currentWindow = -1;
this._thumbnailTimeoutId = 0;
this._motionTimeoutId = 0;</code>

While the underscore prefix in JavaScript is purely a convention, it serves a valuable purpose for developers seeking to establish a distinction between public and private elements within their classes. By adhering to this convention, it becomes clear that certain methods and properties should be treated as internal to the class, discouraging external access.

In conclusion, the underscore prefix in JavaScript is a convention that aligns with the common practice of using it to denote private members. Although not explicitly enforced by the language, it conveys intent and encourages encapsulation, making it a useful convention to adopt.

The above is the detailed content of Does Underscore Prefix in JavaScript Truly Enforce Private Members?. For more information, please follow other related articles on the PHP Chinese website!